I'm dealing with a lot of legacy code with slightly invalid POD markup.
(It's used as pure multiline documentation without being ever processed by a POD parser, but is still properly ignored by the Perl parser.)
Especially newlines are missing around =POD lines, most "newer" POD parsers are quite tolerant about it.
=h1 ------------------------------------------------------- DEFAULT_getaction => bla bla => blubber di blub =cut ------------------------------------------------------ sub DEFAULT_getaction{ my( $cmd, $sth, @row , $jahrpr ) ; # ...
Problem is I need to read this code and cperl-mode is pretty strict about the specifications and stops syntax highlighting of the code thinking it still belongs to POD.
Does anyone know a quick hack to make cperl-mode equally tolerant and parse according to Perl and not according to POD-specifications? (like Komodo does).
(no I can't change the old codebase yet to valid POD)
Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!
PS: see also
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |