You took that out of context. There is no contradiction. You were the one who implied the program file had mixed newline types. I only got out the hex editor to rule out the possibility. All the newlines in the program file have 2 bytes as I stated already.

The offsets I'm referring to in the original post are the offsets shown in the program output. 468 480 493 505 are the offset positions from the array that was created from "tell DATA". By taking the differences between sucessive numbers I could see that adding a newline in the DATA section changed the difference from 12 to 13. 493-480=13; 480-468=12

Adding a new line in the Main Code caused all offsets displayed in the program output to be shifted by 2.

Update: I just got the hex editor out again, all the dust has been brushed off now. The positions of the next character after each of the __DATA__ lines is as follows:

from Hex edit    From program output in OP
0x1D6 => 470     # 470 (the same)
0x1E4 => 484     # 482 different, just like I said.
0x1F4 => 500     # 495
0x202 => 514     # 507

[download]

It confirms what I've been saying all along.

In reply to Re^4: Unexpected result using tell/seek within the __DATA__ file by Gulliver
in thread Unexpected result using tell/seek within the __DATA__ file by Gulliver

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.