Re: Perl5 -> Perl 6 Translations Design Document

2006-06-06 Thread Sage La Torra
"interpolative context" ment the perl 5 side, where the double quotes should cause interpolation. Maybe not the best phrase to identify it, now that you mention it. Sage On 6/6/06, Aaron Crane <[EMAIL PROTECTED]> wrote: Sage La Torra writes: > http://infohost.nmt.edu/~slatorra/conversionstageo

statement-ending } with if

2006-06-06 Thread Daniel Hulme
Can someone explain to me how } on a line on its own can end a statement (as described in the second section of S04), but the following still works? if $condition { ... } else { ... } i.e. Why doesn't the } on the fourth line terminate the if statement, leaving the compiler terminally confuse

~~ with *

2006-06-06 Thread Daniel Hulme
I only vaguely recall the discussions a while back about what smart-matching against Booleans should do. IIRC, there are two positions, and a good argument for either side: C<$foo ~~ True> means C; C<$foo ~~ False> means C or C<$foo ~~ True> means C; C<$foo ~~ False> means C The first of these ad

Re: Perl5 -> Perl 6 Translations Design Document

2006-06-06 Thread Aaron Crane
Sage La Torra writes: > http://infohost.nmt.edu/~slatorra/conversionstageone.txt You say this: -Hash in interprative context: "%hash" -> "%hash{}" (also @{[...]} -> {...}) Hashes don't interpolate in Perl 5, so that's not an issue (unless I'm misunderstanding what you meant). But using "{.