6 ms·
Yay for (some) Perl support! The Perl validation seems to be restricted to "compile with warnings", despite "perlcritic" being now almost 15 years old, predati
by mfontani 6y ago
Yay for (some) Perl support!
The Perl validation seems to be restricted to "compile with warnings", despite "perlcritic" being now almost 15 years old, predating both some other linters' and even some other languages' very existence.
I'll try to see how feasible it'd be to add it as a ("the"?) Perl linter to be used as using just the compilation step to infer everything's fine doesn't really satisfy the role a linter is meant to have.
- zkoppert 6y agoYes please! Feel free to open up an issue and collaborate with others to get it added! https://github.com/github/super-linter/issues https://github.com/github/super-linter/issues
- jwilk 6y agoAlso note that "perl -c" can't be used securely against untrusted code: $ echo 'BEGIN{`cowsay pwned > /dev/tty`}' > test.pm $ perl -Mstrict -cw test.pm _______ < pwned > ------- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || test.pm syntax OK
- obrajesse 6y agoAlso, it looks like the perl linter only triggers against .pl files and not .pm files