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

[Nathan Wiger]

> So is this a consensus?:
> ----
> It is proposed that Perl introduce a new prefix '^', which indicates a
> placeholder. This can be used in any of the following ways:
> - ^identifier: named placeholder
> - ^_: anonymous placeholder
> - ^0, ^1, ...: positional placeholder.

I think this sounds good - great, actually. It's really flexible.

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
   /^^foo/;    # ok
   /^foo/;     # 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.

-Nate