The metric is: is there a way which keeps my subclass a) isolated and encapsulated from any implementation details of the superclass b) while later letting me break this subclasses’ encapsulation iff I so choose? I explained how the approaches known so far fail to satisfy this metric. (Except I missed the fact that xdg pointed out.)
Ruby offers that, which is why I said Perl 5 is not on par with it. (Turns out it is.)
Makeshifts last the longest.
In reply to Re^4: OO in Perl 5: still inadequate
by Aristotle
in thread OO in Perl 5: still inadequate
by Aristotle
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |