Hi

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

  • Re: POD troubles
  • Re: POD troubles
  • (cperl-mode) fontification problem with PODs

    In reply to [Emacs] patching cperl-mode to highlight syntax without POD newlines by LanX

    Title:
    Use:  <p> text here (a paragraph) </p>
    and:  <code> code here </code>
    to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.