The OP is actually intentionally opening and closing the code blocks several times in his post, apparently to facilitate putting portions of the code in <readmore> tags.

The bug is in how the post is written.

The OP, or a janitor could fix it. Best if the OP does, because a Janitor would have to decide whether to put all the code in readmore tags, or none of it; a decision that the OP probably should be the one to make, if possible.

Update: Here is an example of how one small portion of the original post looked in the OP's textbox when 'submit' was clicked:

  const NV nv2 = SvNSIV(b);
  return nv1 < nv2 ? -1 : nv1 > nv2 ? 1 : 0;
}
</code>
</readmore>
<code>
void percent2(SV* sv, ...) {

  I32 i;
  I32 arrayLen;

[download]

Dave

In reply to Re: Single code block split into multiple sequential code blocks. by davido
in thread Single code block split into multiple sequential code blocks. by BrowserUk

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.