Aaron Sherman skribis 2004-04-16 9:52 (-0400):3. You proposed (late in the conversation) that both could co-exist, and while that's true from a compiler point of view, it also leads to: `stuff``stuff`stuff
Huh? No. That is a syntax error.
Actually, no, it's valid and means qx/stuff/.{"stuff"}.{"stuff"} which is of course bogus, but not a syntax error.
A slightly saner example would be: `blah``-1 to get the last line of output from blah.
I agree with Aaron it looks awful, but that simply means a programmer shouldn't do that. If you try hard enough, you'll always be able to write horribly ugly code with some effort.
`$a`b`c` # May or may not give an error, but shocking either way
Syntax error.
This is indeed a syntax error afaics.
Again, saying "look you can combine things to make something ugly" is very poor reasoning. Just because you can write code like
perl -e'connect$|=socket(1,2,1,$/=select+1),pack sa14,2,"\nDBo\$\36";print"d ! @ARGV\nq\n";print$/ +<1>=~/".+?^(.*?)^\./sm' perl
doesn't mean the language is bad. It means I wrote awful code here.
So the only thing I can say in response to these convoluted examples is "don't do that then".
-- Matthijs van Duin -- May the Forth be with you!