IO.read - binary by default?

Hi all,

I'm sick of hitting bugs in 3rd party libs where the issue
is that the 
authors didn't do a binary read on the data. It's hard to
track down 
sometimes and it currently makes creating cross-platform
code more 
difficult.

Is there *any* downside to making IO.read binary by default
(on Windows) 
that anyone can think of?

Thanks,

Dan
_______________________________________________
win32utils-devel mailing list
win32utils-develrubyforge.org
http://rubyforge.org/mailman/listinfo/win32utils-devel

On 9/20/07, Daniel Berger <djberg96gmail.com> wrote:
> I'm sick of hitting bugs in 3rd party libs where the
issue is that the
> authors didn't do a binary read on the data. It's hard
to track down
> sometimes and it currently makes creating
cross-platform code more
> difficult.

I agree

> Is there *any* downside to making IO.read binary by
default (on Windows)
> that anyone can think of?

When reading a text file with rn line endings, it will not
"split" the same.

pth
_______________________________________________
win32utils-devel mailing list
win32utils-develrubyforge.org
http://rubyforge.org/mailman/listinfo/win32utils-devel