Re: Major change proposal

Mark Hahn wrote:

>...
> 
> I'm already less worried about the prototype versus classes thing though.
> Just because he's using the native C# classes doesn't mean he's using the
> native inheritance.  The built-ins don't use any inheritance to speak of and
> the native inheritance doesn't support mutiple inheritance.  You'll notice
> in the sample above he's only inheriting interfaces, not classes.

Inheriting of interfaces is an interesting issue though. It probably 
makes those classes more useful to languages in the rest of the CLR. I'm 
not as sure how to handle that in the case where you don't have classes.

It almost seems to suggest that you SHOULD have a class concept and that 
concept should map exactly to the CLR strengths and weaknesses. So you 
use prototypes within your Prothon code for all kinds of funky runtime 
things and then classes for statically making code available to other 
CLR languages.

  Paul Prescod