Any divergence should have good reasons.

To expand on my comment in Re^5: Recap: The Future of Perl 5, any of the P6 OO semantics which assume stronger type guarantees and identities will be troublesome to implement in Perl. Smartmatch is the best example of that, but type coercions will also be interesting (and not in the fun way).

Not sure what type indenties mean°, but stronger type guarantees could at least happen at runtime, or am I missing something?

Perl 5 already allows to define a type in declarations (see my ) but alas it's only (mostly) a placebo. Would be interesting to know what the plan was...

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}

update

°) you probably mean what JS is handling by the difference between == and === ?

A suitable implementation of UNIVERSAL::new could provide similar default behavior to Perl 6's new. So could a suitable implementation of UNIVERSAL::init - and would be more friendly to "immigrants" from other languages' OO systems - Class::init will be called with an already blessed object, so will only need to perform initializations (and, maybe, validate supplied parameters). (Not surprisingly, overriding new in Perl 6 requires the new class's new method to use bless to create the new object.)

Unfortunately ammending UNIVERSAL will certainly break some CPAN modules.

Just imagine packages trying to catch new in AUTOLOAD.

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}

Unfortunately, true.