Tom Christiansen writes: > if you truly must--are important things. If the perl6:perl5 > relationship is similar in breadth to what we saw in the perl5:perl4 > one, then perhaps, maybe even probably, one will get away with it. > However, if the stretch is appreciably further, I don't think one > will. What you say makes sense, and I agree that radical changes to the language will pose us problems. However, I'm stubbornly not thinking about that until after Larry shows us what perl6 will look like. It may be that Larry will boil down everyone's suggestions into something that looks like perl5, walks like perl5, but quacks like Python and Java's love-child amped up on a batch of cheap Eiffel crank. Nat
- Re: RFC 164 (v1) Replace =~, !~, m//, and s/// with ma... Jonathan Scott Duff
- Re: RFC 164 (v1) Replace =~, !~, m//, and s/// with ma... Tom Christiansen
- Re: RFC 164 (v1) Replace =~, !~, m//, and s/// wi... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//, and s//... Tom Christiansen
- Re: RFC 164 (v1) Replace =~, !~, m//, and... Richard Proctor
- Re: RFC 164 (v1) Replace =~, !~, m//,... Michael Maraist
- Re: RFC 164 (v1) Replace =~, !~, m//,... Tom Christiansen
- Re: RFC 164 (v1) Replace =~, !~, m//,... Michael Maraist
- Re: RFC 164 (v1) Replace =~, !~, m//,... Nathan Torkington
- Re: RFC 164 (v1) Replace =~, !~, m//,... Tom Christiansen
- Creating Perl 6, not Perl++ (was Re: ... Nathan Torkington
- Creating Perl 6, not Perl++ (was Re: ... Nathan Wiger
- Re: RFC 164 (v1) Replace =~, !~, m//,... Tom Christiansen
- Re: RFC 164 (v1) Replace =~, !~, m//,... Chaim Frenkel
- Re: RFC 164 (v1) Replace =~, !~, m//,... Mark-Jason Dominus
- Re: RFC 164 (v1) Replace =~, !~, m//, and... Nathan Wiger