Hello michaelg, did you forget to log in before you posted? If so, maybe now is the time to change your default theme to something that looks different, like i do (i use the Dark Theme). Also, you (and anyone else who reads this who is "guilty" of such) should stop using so many <br> tags. I used to be the same way until someone made me realize that this is a complete waste of your time. Remember, folks use different screen resolutions and application sizes ... when you use <br> tags to make line breaks, you are assuming that the folks who read your post are using the same resolution and application size as you. We don't! So please, stop using <br> tags to make line breaks: let the browser make the desicion,

unless you prefer
to write your posts like haikus
please use the <p> tag
;)

Now then, as for the question ... do as gjb says and look into Inline::Files. It's very easy to grasp, but i wonder if you are missing a better, more maintable solution? Why do you need two DATA sections in one file? I like to use Inline::Files for quick and dirty tests or examples that i post here at the Monastery, but i never use it in production. Sometimes doing it the "old way" is better - in this case, just store them as text files and open them up.

UPDATE:
I guess i'll have to explicitly add that when i say use <p> tags instead of <br/> tags ... i don't mean replace all of the <br/> tags in you post with <p> tags! I mean write a full paragraph and enclose that paragraph in a <p></p> tag pair.

And for the record, i write one sentance paragraphs when they are appropriate. ;)

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to Re: multiple __DATA__ && __END__ by jeffa
in thread multiple __DATA__ && __END__ by Anonymous Monk

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.