RE: Prothon on CPython intrepreter? [PROTHON]

Paul Prescod wrote:

> When your parser sees:
>=20
>   * "abc"
>=20
> It generates a Unicode object instead of an 8-bit object.

What does the * mean?  I'll ignore it.

That would break old Python code that expected an 8-bit object, no?

> When your parser sees:
>=20
> def bar(x=3Dexpression()): pass
>=20
> it converts to something like:
>=20
> def bar(x=3DProthonNoValueProvided):
>     if x=3D=3DProthonNoValueProvided:
>         x =3D expression()

I think you are missing the point.  You are explaining how to implement
Prothon with the CPython interpreter.  I know how to do that. =20

What I was questioning was your idea to make Prothon upwards compatible =
with
Python.  I don't see how that could be done.  My changes to Python would
break existing Python code.

> You could also define a new kind of function object to sit=20
> alongside the=20
> Python function object.
>=20
> Mark Hahn wrote:
>=20
> >=20
> >>-----Original Message-----
> >>From: Paul Prescod [mailto:[email protected]]
> >>Sent: Tuesday, August 10, 2004 9:47 PM
> >>To: Mark Hahn
> >>Subject: Re: Prothon on CPython intrepreter? [PROTHON]
> >>
> >>
> >>Why wouldn't you keep your variant upward compatible with
> >>CPython so it=20
> >>could parse Python code and run Python bytecodes? Then you=20
> get a much=20
> >>bigger standard library.
> >=20
> >=20
> > How could we do that and still fix all the Python problems?  Things=20
> > like separate strings, late eval of default params, etc. would make=20
> > this impossible, wouldn't it?
> >=20
> >=20
>=20
>=20
>=20
>=20