On 5/8/07, Allison Randal <[EMAIL PROTECTED]> wrote:
I actually changed every instance of 'vtable method' to 'vtable function' a few days ago to help clear up the confusion. (A vtable function does have an invocant 'self' but doesn't act as a method in any other way.) But, while I was adding the description of :vtable and :method to the PDD just now, I came up with a naming scheme that's even more useful: 'vtable function' refers to a function pointer stored in the vtable, 'vtable override' refers to a .sub defined in a PIR class to override a vtable function.
I like that differentiation. Now I can eliminate a lot of ambiguity when I talk about vtables :) -- Alek Storm
