Re^2: Perl stops reading __DATA__ when meeting SUB character on Windows (history)

I've been using Perl on Windows, and ^Z has never interrupted reading, even without binmode.

Perl on MS Windows has a long history of stopping reading at CTRL-Z (yes, even in files). That it predates your history with Perl on MS Windows (or just your memory) doesn't cause that history to no longer exist.

Your program produces 4 for me, whether binmode is commented out or not (v5.12).

I recall MS Windows changing its (default) treatment of CTRL-Z in files. This thread makes it clear that Perl did as well.

Some experiments lead me to believe that Perl has/had separate logic for stopping at CTRL-Z when reading Perl source code (and that binmode doesn't/didn't disable/reset that). I'll leave it to others to find that in the Perl source code and determine when that got removed as well (probably after v5.12 but before ikegami's version, which he doesn't mention).

At least, the DATA that Perl v5.12 opened for me stops at CTRL-Z whether binmode has been called on it or not (even after I control for the buffering problem I had experienced before and described elsewhere in this thread) while a DATA that I open myself reads CTRL-Z just fine, whether binmode is used or not.

- tye

Comment on Re^2: Perl stops reading __DATA__ when meeting SUB character on Windows (history)

Replies are listed 'Best First'.
Re^3: Perl stops reading __DATA__ when meeting SUB character on Windows (history) by ikegami (Patriarch) on Jan 06, 2014 at 11:54 UTC
That it predates your history with Perl on MS Windows (or just your memory) doesn't cause thaat history to no longer exist. 1. The OP is using binmode. That should never stop at ^Z! 2. Unless you're saying the OP is using a Perl older than 5.6, I don't see your point. I consider anything older than 5.8 irrelevant unless explicitly mentioned. Your program produces 4 for me, whether bindmode is commented out or not (v5.12). Then I ask you the same question I asked the OP: Could I see your `perl -V` output? Update: I'm sure I had an old version of Perl that didn't treat ^Z specially, but it doesn't seem to be the case. It does appear to be a new fix, so disregard the request. I couldn't test until now.	[reply] [d/l]
Re^4: Perl stops reading __DATA__ when meeting SUB character on Windows (commit) by tye (Sage) on Jan 06, 2014 at 18:07 UTC
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	[reply]
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]
Re^6: Perl stops reading __DATA__ when meeting SUB character on Windows (commit) by tye (Sage) on Jan 06, 2014 at 19:02 UTC
Re^7: Perl stops reading __DATA__ when meeting SUB character on Windows (commit) by ikegami (Patriarch) on Jan 08, 2014 at 14:55 UTC
Some notes below your chosen depth have not been shown here
Re^3: Perl stops reading __DATA__ when meeting SUB character on Windows (history) by Anonymous Monk on Jan 06, 2014 at 02:00 UTC
Um, do you have some code to demonstrate that? I tried and "Ctrl-Z" doesn't change DATA one way or another, I used v5.8.9 My codes Re: Perl stops reading __DATA__ when meeting SUB character on Windows (ddumper), Re^2: Perl stops reading __DATA__ when meeting SUB character on Windows (Ctrl-Z on STDIN) My recollection of perl 5.6 is that it behaved the same way, only when using `perl -` does ctrl-z play a role	[reply] [d/l]