L
Lennon Day-Reynolds
Okay, maybe I just need to take a break from coding for a couple of
hours, but I can't for the life of me figure out what's going wrong
with this code:
--
BLOCKSIZE=1024*256
open('testdata.in') do |input|
open('testdata.out') do |output|
while (chunk = input.read(BLOCKSIZE)) do
output.write(chunk)
end
end
end
--
On Linux with 1.8.2-preview2, it works as expected (and much faster
than I anticipated, which is good). On Windows XP using the latest
one-click, it terminates after a single iteration through the 'while'
loop. Changing the blocksize doesn't make a difference; neither does
using a different looping construct.
It seems like this is a bug in the Ruby interpreter, but it also seems
so basic as to be unlikely to have slipped under the radar in testing.
Can anyone else confirm this behavior? I'll try again in a few hours
when I get home, but would like to stop banging my head against the
problem sooner than that, if possible.
hours, but I can't for the life of me figure out what's going wrong
with this code:
--
BLOCKSIZE=1024*256
open('testdata.in') do |input|
open('testdata.out') do |output|
while (chunk = input.read(BLOCKSIZE)) do
output.write(chunk)
end
end
end
--
On Linux with 1.8.2-preview2, it works as expected (and much faster
than I anticipated, which is good). On Windows XP using the latest
one-click, it terminates after a single iteration through the 'while'
loop. Changing the blocksize doesn't make a difference; neither does
using a different looping construct.
It seems like this is a bug in the Ruby interpreter, but it also seems
so basic as to be unlikely to have slipped under the radar in testing.
Can anyone else confirm this behavior? I'll try again in a few hours
when I get home, but would like to stop banging my head against the
problem sooner than that, if possible.