> 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 "found foo" } /
>>
>> The latter complains about "Statement not terminated properly".
>>
> this is old PGE syntax that hasn't yet been updated to match S05. it's a
> bug.
>
> or maybe, you can say that closures inside regexes aren't supported
> yet, but rakudo has a feature that allows {{PIR}}} to work.
> ~jerry
Thanks for the info. I'll try to learn enough to write a PGE patch to
support {PIR} notation. Given the ubiquity of the {{PIR}} notation I will
probably try to see if I can make it backward compatible, with an eye
toward deprecating it.
Chris
