[#7809] uninit bug in yaml/emitter.c — "Pat Eyler" <rubypate@...>
During our hacking night, we also looked at an UNINIT bug in yaml/emitter.c
[#7813] :!~ not a symbol — noreply@...
Bugs item #4344, was opened at 2006-05-03 17:41
[#7818] (security-related) patch to ALLOC macros to prevent integer overflow bugs — "Dominique Brezinski" <dominique.brezinski@...>
While fixing the integer overflow in rb_ary_fill(), it occurred to me
[#7833] segfault on Proc#call after setting a trace_func — Mauricio Fernandez <mfp@...>
$ cat bug2.rb
[#7843] Possible YAMl bug in 1.8.4 — Damphyr <damphyr@...>
OK, while parsing the td2 data from the ruby-lang website we stumbled on
Its probably a bug. I'm not familiar with the specifics, but Ruby
[#7858] Ruby threads working with native threads — "Francis Cianfrocca" <garbagecat10@...>
I recently wrote a network-event extension for Ruby ("eventmachine" in
[#7865] Strange interactions between Struct and 'pp' — noreply@...
Bugs item #4457, was opened at 2006-05-12 17:13
[#7872] Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...>
All, I needed a nonblocking socket connect for my asynchronous-event
In article <3a94cf510605140559l7baa0205le341dac4f47d424b@mail.gmail.com>,
How about introducing the method Socket#set_nonblocking, or alternatively
Hi,
Well, it's ok then. I'm comfortable adding in the nonblocking
Hi,
How about Socket#nbconnect and Socket#nbaccept?
On 5/15/06, Francis Cianfrocca <garbagecat10@gmail.com> wrote:
In article <1147709691.180288.28647.nullmailer@x31.priv.netlab.jp>,
[#7881] Segfault on x86_64 when built with -O0 in CFLAGS — noreply@...
Bugs item #4491, was opened at 2006-05-16 12:46
[#7882] reproducible bug in DRb on OSX — cremes.devlist@...
I've been tearing my hair out the last few days trying to track down
[#7909] SCRIPT_LINES__ issue when loading a file more than once — Mauricio Fernandez <mfp@...>
SCRIPT_LINES__ is an obscure feature very few people care about, but I happen
On Fri, May 19, 2006 at 06:46:05PM +0900, Mauricio Fernandez wrote:
Hi,
[#7923] Nonblocking accept — "Francis Cianfrocca" <garbagecat10@...>
Thanks to the Matz and colleagues for adding the *_nonblock functions. They
[#7928] set_trace_func: binding has wrong self value for return events — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...>
Moin.
Florian Growrote:
[ ruby-Bugs-4339 ] Ruby fails float 80 test in stable tarball (2 May 2006) when compiled with Mingw
Bugs item #4339, was opened at 2006-05-02 19:56
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=4339&group_id=426
Category: Core
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Jos辿 Soares Augusto (jasa)
Assigned to: Nobody (None)
Summary: Ruby fails float 80 test in stable tarball (2 May 2006) when compiled with Mingw
Initial Comment:
Hi all
After compiling Ruby stable with Mingw I get
$ ./ruby -v
ruby 1.8.4 (2006-05-01) [i386-mingw32]
the 'make check' command produces:
$ make check
not ok float 80 -- ./sample/test.rb:1209
test failed
make: *** [test] Error 1
I changed the sample/test.rb code to have more info on the issue:
........ start at line 1204 in sample/test.rb .....
#s = "3.7517675036461267e+17"
#test_ok(s == sprintf("%.16e", s.to_f))
# NEXT 2 LINES ADDED BY ME #######
print ">>>",f,"\n"
print ">>>",sprintf("%.16e", f).to_f,"\n"
f = 3.7517675036461267e+17
test_ok(f == sprintf("%.16e", f).to_f)
.............................................
The result:
$ ./ruby sample/test.rb
assignment
ok 1
ok 2
ok 3
.......................
ok 77
ok 78
ok 79
>>>3.75176750364613e+017
>>>3.75176750364613e+017
not ok float 80 -- sample/test.rb:1209
bignum
ok 1
...........................
Apparently the two strings are equal. Has this something
to do with the '==' operator?
Thanks
Jos辿 Soares Augusto
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=4339&group_id=426