Allison Randal wrote:
Class is the base for all classes. I can see the value of stripping away 
any methods that may interfere with a particular HLL's concept of how a 
class should behave, so we'll do that. And what should we call the 
subclass of Class that adds lots of methody syntactic sugar over the 
top? My best suggestion at the moment is ParrotClass, as a contrast to 
PerlClass, PythonClass, RubyClass, etc.
Then again, the syntactic sugar methods could just be a role applied to 
Class, once we get roles working for low-level PMCs.
Allison

Reply via email to