Re^3: I would have expected a syntax error here

indirect already exists on CPAN:

>perl -M-indirect -wle "got to here today! (20180520)"
Indirect call of method "here" on object "today" at -e line 1.
Indirect call of method "got" on object "to" at -e line 1.
Can't locate object method "here" via package "today" (perhaps you for
+got to load "today"?) at -e line 1.
[download]

>perl -wle "got to here today! (20180520)"
Can't locate object method "here" via package "today" (perhaps you for
+got to load "today"?) at -e line 1.
[download]

You can put it either into PERL5OPT or just at the top of your code:

no indirect;
[download]

Comment on Re^3: I would have expected a syntax error here Select or Download Code

Replies are listed 'Best First'.
Re^4: I would have expected a syntax error here by roboticus (Chancellor) on Oct 19, 2018 at 17:45 UTC
Corion: While I'm going to try to use the yadda operator, I think I'll stick this in my PERL5OPT since: I'm already using PERL5OPT, who knows how many of these bombs may be ticking on my hard drive, and I don't know how long it'll take me to get into the habit of using ... ...roboticus When your only tool is a hammer, all problems look like your thumb.	[reply]
Re^4: I would have expected a syntax error here by LanX (Saint) on Oct 19, 2018 at 18:30 UTC
Nice ... ... but I think it should allow to add new as exception. (couldn't find it) There is far too much legacy code using an indirect new as constructor. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}	[reply]
Re^5: I would have expected a syntax error here by Corion (Patriarch) on Oct 19, 2018 at 18:37 UTC
You don't need to make it fatal and you also don't need to enable it globally. If it is for your own code, you can slowly fix that code, eliminating those warnings.	[reply]