I agree that cperl's syntax highlighting is among the best.

But it can't help catching typos in variable-names or scoping problems. That's where flymake et al. comes very handy.

I have never refactored code to use strict; because all of my code has been written under strict (command-line one-liners excepted), but when I have had typos in variable names, I have always had great success by simply running the script at a terminal and letting perl point out the errors.

Since this is presumably functioning code, we can expect that there will be no variable-name typos. The simplest option for moving to strict would be to add use strict; and then use vars at top-level, listing the variables already used until all are declared. Narrowing the scopes to lexicals can then be done incrementally, using grep or Emacs' M-x occur to identify where each name is mentioned in the code and understanding of the program to determine where values can be reduced to narrower scopes.

> I have always had great success by simply running the script at a terminal and letting perl point out the errors.

You never tried flymake-mode, right? :)

And why do you run it in a terminal instead of a compilation buffer?

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}