> The interesting thing about ... is that you have to be able to
> deal with it a statement with an implied semicolon:
>
> print "foo";
> ...
> print "bar";
We already have plenty of statements with implied semicolons:
print "foo";
for @list {}
print "bar";
> Either that, or it's a funny unary operator that can take 0 or 1 argument.
>
> That might let you parse these too:
>
> print (1, 2, 3, ...) or die;
I think this is fraught with peril. I'd have expected:
print (1, 2, 3, ...) or die;
to print
12345678910111213141516171819202122232425262728etc
rather than:
123Executed stubbed code at demo.pl, line 123
BTW, I propose the this new operator be pronounced "yadda yadda yadda". :-)
Damian
