Re^4: File::Slurp bug? Should I bother?

I just experimented a little using

This is perl, v5.6.1 built for MSWin32-x86-multi-thread
-> sysread convert CRLF to LF.

This is perl, v5.8.0 built for MSWin32-x86-multi-thread
-> sysread does **not** convert CRLF to LF.

Both are ActiveState builds.

Apparently, sysopen/sysread's behaviour changed in 5.8 wrt to CRLF conversion. It used to convert, but now it doesn't. I don't see this mentioned in Perl 5.8's perldelta or anywhere else. It seems to be an (unintentional?) side-effect of switchting to PerlIO.

Comment on Re^4: File::Slurp bug? Should I bother? Select or Download Code

Replies are listed 'Best First'.

Re^5: File::Slurp bug? Should I bother?
by chester (Hermit) on Sep 07, 2005 at 18:30 UTC

Perl 5.8.1

"As of the 5.8.0 release, sysopen()/sysread()/syswrite() do not behave like they used to in 5.6.1 and earlier with respect to "text" mode. These built-ins now always operate in "binary" mode (even if sysopen() was passed the O_TEXT flag, or if binmode() was used on the file handle). Note that this issue should only make a difference for disk files, as sockets and pipes have always been in "binary" mode in the Windows port. As this behavior is currently considered a bug, compatible behavior may be re-introduced in a future release. Until then, the use of sysopen(), sysread() and syswrite() is not supported for "text" mode operations.'

File::Slurp

[reply]


Do you know where your variables are?
	PerlMonks