Yes, but with use strict; in force, why does perl -c give no errors for the two PRINT barewords?
| [reply] [d/l] [select] |
Indirect object notation. Method names aren't checked for existence before runtime.
($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
| [reply] [d/l] |
Hello choroba,
Yes, ok, thanks, I guess that makes sense: the parser can’t know in advance whether a yet-to-be-imported object has a particular method or not. But it’s still a bit strange:
21:54 >perl -c -Mstrict -wE "PRINT OUT 42;"
-e syntax OK
21:55 >perl -c -Mstrict -wE "PRINT 42;"
Number found where operator expected at -e line 1, near "PRINT 42"
(Do you need to predeclare PRINT?)
syntax error at -e line 1, near "PRINT 42"
-e had compilation errors.
21:55 >perl -c -Mstrict -wE "PRINT;"
Bareword "PRINT" not allowed while "strict subs" in use at -e line 1.
-e had compilation errors.
21:55 >perl -c -Mstrict -wE "PRINT(42);"
-e syntax OK
21:55 >
Why does PRINT 42; produce a compile error, but PRINT(42) not? There’s no possibility of an indirect object in the latter case, is there?
| [reply] [d/l] [select] |