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

[Nathan Wiger]

> > There's two potential solutions here:
> > 1- Use '_'
> > 2- Use '^', but increase the strictness of sub calls
> 
> > The second suggestion specifically relies on us deciding that barewords are
> > always evil, so that :
> >   $a = foo;  # Error! Evil bareword! Return to firey depths of hell!

Seems to me that a leading _ is worse for this than ^:

   $a = _foo;      # definitely sub call

I write subs all the time with a leading _ to denote they're "private".

Main difference is _ is a valid sub/var/etc character. ^ is not.

-Nate