Alek Storm wrote:
Again, the only part of :method that :vtable needs to imply is the
part that
sets the invocant in the proper register and makes 'self' available
within
the body of the method.
So, that still means :method can mean two different things, depending
on whether :vtable is present or not. That's still bad.
How so? Without :vtable, :method adds a method to the class. With
:vtable, :method adds a method to the class.
Oh, I should add, under the new OO spec, methods don't get entries in
the "namespace" either, they only get entries in the class itself (since
you may have multiple classes with different implementations pointing to
the same namespace). It's really that fact more than anything else that
has changed my thinking on the appropriate division of sub modifiers.
Allison
