On Mon, Oct 27, 2008 at 04:07:39PM -0500, [EMAIL PROTECTED] wrote:
> > On Sun, Oct 26, 2008 at 10:45 PM, Chris Dolan <[EMAIL PROTECTED]> wrote:
> >> S05 always uses single curlies for closures, but throughout Parrot, code
> >> seems to use double curlies in PGE regexps. Why is that?
> >>
> >> That
> On Sun, Oct 26, 2008 at 10:45 PM, Chris Dolan <[EMAIL PROTECTED]> wrote:
>> S05 always uses single curlies for closures, but throughout Parrot, code
>> seems to use double curlies in PGE regexps. Why is that?
>>
>> That is, why this:
>> m/ foo {{ say "found foo" }} /
>> and not this:
>> m/ foo
On Sun, Oct 26, 2008 at 10:45 PM, Chris Dolan <[EMAIL PROTECTED]> wrote:
> S05 always uses single curlies for closures, but throughout Parrot, code
> seems to use double curlies in PGE regexps. Why is that?
>
> That is, why this:
> m/ foo {{ say "found foo" }} /
> and not this:
> m/ foo { say "f
S05 always uses single curlies for closures, but throughout Parrot,
code seems to use double curlies in PGE regexps. Why is that?
That is, why this:
m/ foo {{ say "found foo" }} /
and not this:
m/ foo { say "found foo" } /
The latter complains about "Statement not terminated properly".
C