NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
help them think they understand.
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
kidding, right? (Score:1)
I mean, I use "HASH(0x1731300)HASH(0x174c918)" all the time.
I think I saw it on the fourth read-through.
If not a syntax error, at least a warning.
-- dagolden
Re:kidding, right? (Score:1)
Personally, I think that this is an example of something which should be another type of compile time error, which we don't have: semantic error. Specifically, the language technically allows it, but it has meaning that nobody would ever conceivably want.
As I understand that what I can conceive is limited, I'd probably add a runtime option to perl to disregard semantic errors. However, without that option, I'd have it complain about interpolating the literal hash and exit immediately.
Reply to This
Parent