On Mar 28, 2008, at 2:07 PM, Henry Minsky wrote:
Although in this case we're screwed because
it calls super.setY, so we really need to make this a singleton
class...
What's the rule? Cannot call super methods when declaring an event
method, or what?
Well, at the moment it would have to be that you cannot define a
method on an instance , which
calls super.something, because it won't be compiled as a real class
method. it will just be a function
closure which is sitting around as a property on the object.
People expect this to work, which is why we're going to have to bite
the bullet and make tag compiler
emit singleton class declarations for every instance that declares a
method which calls super(). And if we're
not emitting a singleton class declaration, then we have to make
sure NOT to put the "override" keyword
before the "function ..." expression, because it is only allowed
when you're really defining a method of a class.
Got it, thanks. Certainly sounds like one of the known restrictions
for Monday's release.
--
Don Anderson
Java/C/C++, Berkeley DB, systems consultant
voice: 617-547-7881
email: [EMAIL PROTECTED]
www: http://www.ddanderson.com
