On Wed, Apr 21, 2004 at 03:37:23PM -0400, John Macdonald wrote:
What about "$x\n"? The backslash already has meaning in strings
I use hash elements far more often outside than inside strings, so I could
live with having to write $x«foo» for interpolated hash elements.
Anyway, you're missing the
On Wed, Apr 21, 2004 at 09:19:12PM +0200, Matthijs van Duin wrote:
> On Wed, Apr 21, 2004 at 01:02:15PM -0600, Luke Palmer wrote:
> > macro infix:\ ($cont, $key)
> > is parsed(/$?key := (-?\w* | \d+)/)
> > {
> > if $key ~~ /^\d+$/ {
> > "($cont).[$key]";
> > }
> >
On Wed, Apr 21, 2004 at 01:02:15PM -0600, Luke Palmer wrote:
macro infix:\ ($cont, $key)
is parsed(/$?key := (-?\w* | \d+)/)
{
if $key ~~ /^\d+$/ {
"($cont).[$key]";
}
else {
"($cont).«$key»";
}
}
That does all the magic at compile t
Matthijs van Duin writes:
> On Tue, Apr 20, 2004 at 10:55:51AM -0700, Larry Wall wrote:
> >The flip side is that, since we won't use C<`> as an operator in Perl
> >6, you're free to use it to introduce any user-defined operators
> >you like, including a bare C<`>. All is fair if you predeclare.
>
On Tue, Apr 20, 2004 at 10:55:51AM -0700, Larry Wall wrote:
The flip side is that, since we won't use C<`> as an operator in Perl
6, you're free to use it to introduce any user-defined operators
you like, including a bare C<`>. All is fair if you predeclare.
Most languages won't even give you that
