News for hackers. Stuff that matters.

A comment on All About EOF (2012).

Re:All About EOF (2012) by jokh on Monday March 11, 2019 @01:40PM (#19360962)
Why doesn't Windows drop the purported compatibility with CP/M and get rid of control-z being a special file marker at this point? Lots of legacy code relying on it?
[ Parent | on HN ]
Re:All About EOF (2012) by JdeBP on Tuesday March 12, 2019 @05:07AM (#19366434)
It's not in Windows in the first place. The headlined article does explicitly say this.

It's library code in a large number of applications programs.

* http://jdebp.eu./FGA/dos-character-26-is-not-special.html

[ Parent | on HN ]
Re:All About EOF (2012) by Arnavion on Tuesday March 12, 2019 @03:22AM (#19366056)
FWIW it's generally advised to not open files in text mode on Windows anyway. The handling of \x1A is one reason. The automatic mangling of newlines into Windows newlines is another.

Edit: And while cmd's type does process it, modern stuff like PS's Get-Content does not.

[ Parent | on HN ]
Re:All About EOF (2012) by Thorrez on Tuesday March 12, 2019 @02:58AM (#19365962)
Someone could even write new code that relies on it.
[ Parent | on HN ]