20 minutes
Intermediate
English
Statically typed languages are on the rise these days.
One particular advantage that statically typed languages bring is the ability to run static analysis on the source code. Static analysis allows you to find unused variables, find irregular coding styles within the source, and analyze dependency between modules/classes WITHOUT actually running the code.
On the other hand, dynamically typed languages such as Perl have their advantages. Static analysis, however, is not in the list of those advantages. In fact, it's incredibly hard to perform static analysis on Perl.
But wouldn't it be cool if you could do it? You would be able to harness the true power of Perl, all while being able to systematically check for potential problems before running the code.
In this talk, I will be talking the state of things around performing static analysis on Perl code: tools, attempts, and also Perl::Lint, which is a tool I have created with the help of TPF grants to perform static analysis.
(English translation provided by Daisuke Maki, thank you very much!)