I don't know if Larry has considered their disposition yet.
*whisper*Banish them... they were a terrible hack... develop a general purpose mechanism instead of this abomination...*whisper*
Perl's laissez faire approach to OO.
Staying in Perl 6. But being augmented by a second, B&D, OO mechanism.
BTW, those who are complaining are, for the most part, neither grinding axes nor bondage freaks. They are generally people with large commercial OO production systems to build, who would prefer not to have to jump through so many hoops to get compile-time checking, declarative attributes, pre- and post-conditions, strong encapsulation, etc. That is, they genuinely need all those valuable, scalable OO tools that Perl 5's laissez faire approach to OO trades off.
I've built several large (some very
large) commercial OO production systems and never found Perl's OO lacking in any significant way. (For that matter I've built effective OO systems in C as well!) Most of the nits you listed can be solved with good design and mild discipline by the programmers. No whips, chains, or leather required.
Personally, if I can use Perl's OO as I currently do I'll remain happy as a pig in mud.