in reply to Re^6: RFC: feature proposal re code in @INC
in thread RFC: feature proposal re code in @INC

But these are things that can usually be spotted very quickly. Which leads to the second part of the OP hope: "At some point, they do get fired...".

In my understanding, what is really scaring the OP is that someone can write apparently innocent code and make a mess that's hard to spot. Probably, some kind of code analysers (or some "flagging" feature inside perl itself, with the lower "p", who knows?) could help to spot if some program uses these "gray" features, and a company could enforce that these should not be used.

Something along these lines (but I really don't know if it's doable) would allow a company decide the "level of cleverness" allowed, while letting the whole Perl community benefit from Perl's un-orthogonality (which I truly love).

Flavio
perl -ple'$_=reverse' <<<ti.xittelop@oivalf

Don't fool yourself.
  • Comment on Re^7: RFC: feature proposal re code in @INC

Replies are listed 'Best First'.
Re^8: RFC: feature proposal re code in @INC
by diotalevi (Canon) on Jan 27, 2006 at 15:36 UTC

    Have you seen Perl::Critic? It does things like this. You can make cleverness plugins for B::Lint too.

    ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊