From: daz <dooby@...10.karoo.co.uk>
Date: 2005-07-22T15:54:07+09:00
Subject: Re: [ ruby-Bugs-2131 ] ruby ( v183) bcc32: using Socket.new with timeout -> files not closed


----- Original Message ----- 
From: H.Yamamoto


>
> Umm, it works for me...
>

I was sure it would ;-/


> [...]
> But it should work for now because RTL are "dynamically" linked from this change.
>
> Can you try clean build? "-tWR -tWC" should be there.
>

I knew about that change ... "-tWR -tWC" were there.


> # And be sure not to mix different borland dll.

( I have C++Builder4 installed but it is isolated from bcc 5.5.1 )


Clean build, default options, same problem :-(

  D:\usr\bin>ruby -v rbnet.rb
  ruby 1.9.0 (2005-07-16) [i386-bccwin32]
  ["Net::HTTP", "1.126", "1.1"]
  D:/USR/lib/ruby/1.9/net/protocol.rb:70:in `close': Bad file number (Errno::EBADF)
  [...]


My binaries may work OK on a machine without ZoneAlarm ?

Here's my ruby.exe & bccwin32-ruby19.dll built on 98se.
http://www.d10.karoo.net/public/temp/rb19bc5.zip  (314k)
MD5: a236bdc0a78de2efd33472e3fe720b8b


Actually, I think any Windows user _without_ ZoneAlarm could
verify if the included script works for them.

This is my Borland runtime (CC3250.DLL) in case anyone needs it, also.
http://www.d10.karoo.net/public/temp/cc3250.zip   (330k)
MD5: 81b0f40f05d7393275da3c5457d1312e

Just unzip everything into a single temp folder, then ...
  C:\temp42>ruby rbnet.rb


daz

Windows sockets vs. Berkeley sockets
http://tangentsoft.net/wskfaq/articles/bsd-compatibility.html