RE: Re: [Python-Dev] Re: Prothon on CPythonintrepreter? [PROTHON]

Lenard Lindstrom wrote:

>Yes it is too bad. I personally do not think it would have=20
>been as big a job as everyone put on. .Net will not be a easy=20
>either.=20

I have been looking at both and the deeper I get into both the bigger =
the
difference I see.  The CLR was designed for multiple languages on top of =
one
object space and CPython was not. .Net may come from the dark side, but =
it
is really well architected. =20

The IronPython code is really slick.  I added my new Bytes type to
IronPython last night in a couple hours and it worked.  It is =
implemented
internally as a simple byte[] in C# for maximum performance.  When I =
started
I didn't really know what I was doing and I stuck in the byte[] type and
Jim's code almost handled it automatically by introspection.

I've been trading emails with Jim Hugunin, the author of IronPython.  He =
has
been really helpful.  Of course his new job at Microsoft is to help =
people
like me. :-)  He has even offered some mechanism to make our codebases
compatible (merge them?).  The Python folks are ultra-nice but they
certainly wouldn't make that offer. :-)