Im glad you mentioned Perltidy. In many respects perltidy already contains a tokenizer that handles the majority of perl constructs, as well as mechanisms for identifying some of the more pain in the ass errors (such as a missing { ( [ Also there are tools such as B::Deparse that would probably help with the task of resolving (semi)ambiguous statements (otoh that might not be the best plan for security reasons... :-)

Much respect to adamk for trying a hard task, but I would hope he at least has a look at the existing codebase and would prefer that he joins forces with those authors. At the very least it would make a very popular tool like Perltidy even better...

my $.02;

Yves / DeMerphq
--
When to use Prototypes?