> Just as simply,
>
> - $foo is the variable 'foo'
> - ^foo is the placeholder 'foo'
> - $_ is the default variable
> - ^_ is the default placeholder
Yeah, I personally can read this much clearer. Peter also mentions that
__ is hard to distinguish from _, unless they're right next to each
other, and I think this is a very valid point.
I think the principle of a "general purpose placeholder" is a good one.
But I think _ is already used so much in Perl that something else is
better. I like ^ since is looks like a carat ("insert your variable
here"), personally.
I would avoid *, though, since typeglobs might not go away, and even if
they do it will be quite a shock is *intendedglob works like
*placeholder in 6 vs. 5 (sure, RTFM, but still...).
-Nate
- Re: RFC 23 (v1) Higher order functions Jeremy Howard
- Re: RFC 23 (v1) Higher order functions Damian Conway
- Re: RFC 23 (v1) Higher order functions John Porter
- Re: RFC 23 (v1) Higher order functions Damian Conway
- Re: RFC 23 (v1) Higher order functions Jeremy Howard
- Re: RFC 23 (v1) Higher order functions Glenn Linderman
- Re: RFC 23 (v1) Higher order functions Damian Conway
- Different higher-order func notation? (was Re: RFC 23... Nathan Wiger
- Re: Different higher-order func notation? (was Re... Jeremy Howard
- Re: Different higher-order func notation? (wa... Mike Pastore
- Re: Different higher-order func notation?... Nathan Wiger
- Re: Different higher-order func nota... Jeremy Howard
- Re: Different higher-order func ... John Porter
- Re: Different higher-order func nota... Damian Conway
- Re: Different higher-order func nota... Mike Pastore
- Re: Different higher-order func nota... John Porter
- Re: Different higher-order func notation?... Ken Fox
- Re: Different higher-order func nota... Mike Pastore
- Re: Different higher-order func ... Nathan Wiger
- Re: Different higher-order func ... Ken Fox
- Re: Different higher-order func ... Jeremy Howard
