On Aug 22, P T Withington wrote: > Interesting. The new class substrate does something very similar: it > has both an instance initializer and a class initializer and the class > initializer is called on the class prototype. In the class substrate, > the class initializer is called with this bound to the class that it is > the initializer for and the prototype is passed as an argument. The > class initializer(s) are invoked from least- to most-specific for each > subclass. I'm not saying this is the right way to do it, just that's > what happens currently. It seems 6/1 whether the class or the prototype > is this and the other the argument. I'm loathe to waste a prototype > slot pointing back to the class if I don't have to since it's just one > more name taken from the user. Huh. Seems like the advantage of calling it on the prototype is that you can use your regular call inherited mechanism. Maybe I'll just pass in the class.
A _______________________________________________ Laszlo-user mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-user
