Re: Different higher-order func notation? (was Re: RFC 23 (v1) Higher order functions)

[Damian Conway]

   > As for the regexp issue, just to clarify there's only one ambiguous case
   > we need to work out that I can see:
   > 
   >    /.*^foo/;   # ok

But:    /.*^foo/m;  #ambiguous

   > We could undo the ambiguity like so:
   > 
   >    /^{foo}/;   # like ${foo} and @{foo} and %{foo}
   > 
   > In fact, this seems built-in if we follow the same var conventions. We
   > can make ^ bind to {} as tightly as we need.

That would be the right solution. And of course one could use the {} anywhere
necessary or desirable:

        my $sin_deg = sin(180*^{_}/$pi);

Damian