Michael Maraist writes: > Compatibility is going to have to be maintained somehow. And we can either > have some sort of perl6 designator (such as the pragma) to designate > incompatible (and otherwise ambiguous) code, or we're going to have to > continue tacking on syntactic sugar to legacy code. The compatibility path for perl5 to perl6 is via a translator. It is not expected that perl6 will run perl5 programs unchanged. The complexity of the translator and the depth of the changes will be decided by the decisions Larry makes. Nat
- Re: RFC 164 (v1) Replace =~, !~, m//, and s/// with ma... Jonathan Scott Duff
- Re: RFC 164 (v1) Replace =~, !~, m//, and s/// wi... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//, and s//... Jonathan Scott Duff
- Re: RFC 164 (v1) Replace =~, !~, m//, and s//... Tom Christiansen
- Re: RFC 164 (v1) Replace =~, !~, m//, and... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//,... Tom Christiansen
- Re: RFC 164 (v1) Replace =~, !~,... Richard Proctor
- Re: RFC 164 (v1) Replace =~,... Michael Maraist
- Re: RFC 164 (v1) Replace =~,... Tom Christiansen
- Re: RFC 164 (v1) Replace =~,... Michael Maraist
- Re: RFC 164 (v1) Replace =~,... Nathan Torkington
- Re: RFC 164 (v1) Replace =~,... Tom Christiansen
- Re: RFC 164 (v1) Replace =~,... Nathan Torkington
- Creating Perl 6, not Perl++ ... Nathan Wiger
- Re: RFC 164 (v1) Replace =~,... Tom Christiansen
- Re: RFC 164 (v1) Replace =~,... Chaim Frenkel
- Re: RFC 164 (v1) Replace =~,... Mark-Jason Dominus
- Re: RFC 164 (v1) Replace =~, !~,... Nathan Wiger