Ruby Issue Tracking System

03/07/2011

11:35 pm ruby-trunk Bug #4478: hash order preservation fails on 64bit machine

=begin
~$ ruby1.9 -v
ruby 1.9.0 (2006-06-08) [x86_64-linux]
=end

07:40 pm ruby-trunk Feature #4477: Kernel:exec and backtick (`) don't work for certain system commands

=begin
Sorry, Shota, I do not understand why you recategorized this issue as a Feature.
The current behaviour of `...

06:07 pm ruby-trunk Bug #4478 (Rejected): hash order preservation fails on 64bit machine

=begin
On a 32bit machine:
~$ uname -r
2.6.32-5-686
~$ ruby1.9 -e "x={};x[:a]=1;x[:b]=2;p x"
{:a=>1, :b=>2} # ...

05:55 pm ruby-trunk Feature #4477 (Assigned): Kernel:exec and backtick (`) don't work for certain system commands

From documentation and common sense, I would expect that Kernel:exec and backtick (`) work for _all_ kind of system c...

01/09/2009

08:55 pm Ruby 1.8 Bug #993: obsolete "nonblocking IO#read" used in system calls

=begin
Well, I searched in the source. The "nonblocking" warning comes from io.c:io_fread. It is issued only if
a ...

07:48 pm Ruby 1.8 Bug #993: obsolete "nonblocking IO#read" used in system calls

=begin
It is not that easy to reproduce the warning. I am issuing the `ls ..` command every ten seconds, and I get o...

07:02 pm ruby-trunk Feature #994 (Closed): Hash-order preservation should be declared a feature; documentation needs ...

=begin
I would like to come back to a thread from March 2008 in comp.lang.ruby,
http://groups.google.com/group/com...

06:48 pm Ruby 1.8 Bug #993 (Feedback): obsolete "nonblocking IO#read" used in system calls

=begin
Running ruby 1.8.7 under linux, from time to time I get the message
"warning: nonblocking IO#read is obsole...