in reply to Re^3: Perl stops reading __DATA__ when meeting SUB character on Windows (history)
in thread Perl stops reading __DATA__ when meeting SUB character on Windows

Part of the puzzle might be p5git://commit=9b1f1815, which became part of v5.14.

The OP is using binmode. That should never stop at ^Z!

So if Perl hits EOF due to CTRL-Z (while reading source code), then subsequently doing binmode will clear that EOF condition?

- tye        

  • Comment on Re^4: Perl stops reading __DATA__ when meeting SUB character on Windows (commit)

Replies are listed 'Best First'.
Re^5: Perl stops reading __DATA__ when meeting SUB character on Windows (commit)
by ikegami (Patriarch) on Jan 06, 2014 at 18:24 UTC

    If you're asking if it should, then probably not. I have no idea what it actually does.

    I don't see how that's relevant to this situation or the text you quoted. Perl should not have reached the ^Z while reading the source code. It should have found __DATA__ first.

[reply]
[d/l]
      Perl should not have reached the ^Z while reading the source code. It should have found __DATA__ first.

      So how big of a buffer do you suppose is being used when Perl is reading from a file looking for "__DATA__"?

      - tye        

[reply]

        Are you saying it's ok for binmode(DATA, ...) only to take effect partway through the data? No, that's a bug.

        It doesn't matter how big the buffer is. It could be big enough to contain the entire file. The parser can't go changing bytes later in the file unless it knows it's safe to do so or it has a means of restoring them. Otherwise, it breaks DATA.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom