RE: Major change proposal

Paul Prescod wrote:

> And as you say later: the code is open source. Rip off ideas.
> 
> > At first I thought Python would have an unfair advantage 
> over Prothon 
> > in implementation since Python is class-oriented and CLR is 
> > class-oriented, but then I realized that the same phenomenom that 
> > caused me to discover that Python can do anything that 
> Prothon can do 
> > over the last four months is going to cause Python to have the same 
> > implementation difficulties that Prothon will have in the 
> CLR.  

I've read the IronPython code and I'm a bit nervous at this point.  Jim uses
the static classes for the Python built-in types and methods.  He keeps a
separate set of dynamic "reflection" objects on a one-for-one basis with the
static object instances.  This lets the static objects run code at full
speed and the reflection objects store the dynamic attributes.  This kind of
proxying makes quite efficient use of the built-in static objects.  I don't
know if I can pull off a similar trick since there aren't any built-in
prototype-based static objects.

It's too early to get too worried but this is what I'm coming up against
right now.