Melvin Smith wrote: > > > > If you wouldn't want the base implementation to be ignore there is usually > > > some mechanism in C++ and Java for this, how it applies to Perl6 I'm not > > > sure. > > > >I'm not sure either. In fact, I'm not sure what you mean by this > >sentence at all. If it matters, please rephrase it, so we can talk more > >about it. > > Referring to final, private, etc. modifiers that you can use in C++/Java > whenever you don't want someone reimplementing or overriding something. > Will there be such a thing in Perl6? > > I think this is meant more for "Me" (not me) than you.
final and private are completely different concepts as I understand them. At least, I think I understand private to be stuff used by the implementation of methods, that is not available for the general public to see. This is considered a good thing in compiled code where users code to the interface, and cannot see the implementation. In Perl, the implementation is generally visible, and privacy would be somewhat fictitious, albeit perhaps a useful one at times. Final seems to be a way of sealing off a class or method from future inheritance. Generally, the arguments I've seen on OO lists seem to indicate that regardless of how omniscient the original designer is, someone will get an idea for a useful subclass for the class or method, but run into the problem of not being able to extend it because of the superclass implementor's choice to make it final. Hence, final seems to be a concept that is rather un-Perl-ish. -- Glenn ===== Due to the current economic situation, the light at the end of the tunnel will be turned off until further notice.
