[#30545] [Ann] Contribution wanted: identify tickets for 1.9.2 release — Yusuke ENDOH <mame@...>
Hi all --
[#30558] [Feature #3380] Minitest Runner Command — Thomas Sawyer <redmine@...>
Feature #3380: Minitest Runner Command
[#30592] [Bug #3392] Kernel.open Ignores :binmode Key in Opts Hash w.r.t Encoding — Run Paint Run Run <redmine@...>
Bug #3392: Kernel.open Ignores :binmode Key in Opts Hash w.r.t Encoding
[#30602] The `open` Methods and Their Many Arguments — Run Paint Run Run <runrun@...>
I'm documenting Kernel.open, and the related .open methods, for a book
[#30607] [Bug #3395] Ruby does not appear to build against openssl-1.0.0a — Rebecca Menessecc <redmine@...>
Bug #3395: Ruby does not appear to build against openssl-1.0.0a
[#30656] Promote RubyInstaller as better alternative in ruby-lang.org — Luis Lavena <luislavena@...>
Hello,
[#30672] [Bug #3411] Time.local 1916,5,1 #=> 1916-04-30 23:00:00 +0100 — Benoit Daloze <redmine@...>
Bug #3411: Time.local 1916,5,1 #=> 1916-04-30 23:00:00 +0100
Hi,
On Tue, Jun 8, 2010 at 2:58 PM, Benoit Daloze <redmine@ruby-lang.org> wrote:
[#30697] [Bug #3418] IO#putc Clobbers Multi-byte Characters — Run Paint Run Run <redmine@...>
Bug #3418: IO#putc Clobbers Multi-byte Characters
[#30707] [Bug #3420] Module#method calling <=> causes SystemStackError — Florian Aßmann <redmine@...>
Bug #3420: Module#method calling <=> causes SystemStackError
[#30722] [Feature #3424] Source code interaction. [new ideas for ruby 2] — Eloy Esp <redmine@...>
Feature #3424: Source code interaction. [new ideas for ruby 2]
[#30734] [Bug #3428] ri outputs ansi escape sequences even when stdout is not a tty — caleb clausen <redmine@...>
Bug #3428: ri outputs ansi escape sequences even when stdout is not a tty
[#30756] [Feature #3436] Spawn the timer thread lazily — Maximilian Gass <redmine@...>
Feature #3436: Spawn the timer thread lazily
Issue #3436 has been updated by Mark Somerville.
Hi,
(2010/10/08 15:12), Nobuyoshi Nakada wrote:
On Fri, Oct 08, 2010 at 11:12:47PM +0900, Nobuyoshi Nakada wrote:
On Sun, Oct 10, 2010 at 01:27:53AM +0900, Mark Somerville wrote:
On Sun, Oct 10, 2010 at 02:21:41AM +0900, Mark Somerville wrote:
[#30799] PATCH: ENV['key'] = non_string — Ryan Davis <ryand-ruby@...>
Can I commit this please? This drives me bonkers.
Hi,
[#30821] [Bug #3454] Segfault with syscall — Run Paint Run Run <redmine@...>
Bug #3454: Segfault with syscall
[#30855] requires in 1.9 are slower... — Roger Pack <rogerdpack2@...>
Hi all.
[#30882] Was 1.8.7-p299 announced here? — Luis Lavena <luislavena@...>
Hello, tried to look for the release notes or a link, just found the
[#30891] [Feature #3478] Excruciatingly slow pathname implementation — Stephen Touset <redmine@...>
Issue #3478 has been updated by Stephen Touset.
[#30913] String#rindex is faster with Regexps than with Strings? — Kornelius Kalnbach <murphy@...>
hi,
[#30917] [Bug #3487] fiddle pushes arguments in a wrong format — Yuki Sonoda <redmine@...>
Bug #3487: fiddle pushes arguments in a wrong format
On Sun, Jun 27, 2010 at 08:36:45PM +0900, Yuki Sonoda wrote:
[#30927] undefined reference to 'rb_encdb_declare'; ruby-1.9.2-preview3 64-bit on Windows — Chuck Remes <cremes.devlist@...>
[cross-posted to rubyinstaller ML]
On Sun, Jun 27, 2010 at 2:36 PM, Chuck Remes <cremes.devlist@mac.com> wrote:
[#30968] ironruby vs ruby — "C.E. Thornton" <admin@...>
Matz,
On Wed, Jun 30, 2010 at 6:25 AM, C.E. Thornton
Note that Antonio's benchmark compares 64bit IronRuby build against 32bit 1.8.7 MRI and thus favoring MRI.
[ruby-core:30923] [Feature #3491] Pack missing directives for signed types with specified byte-order
Feature #3491: Pack missing directives for signed types with specified byte-order
http://redmine.ruby-lang.org/issues/show/3491
Author: Erik M
Status: Open, Priority: Normal
Category: core
The Array#pack and String#unpack have some directives where the byte-order is specified ("little endian" or "network order"), for unsigned long and for unsigned short. But when it comes to signed long and signed short there is no way to specify byte order, you can only use the platform-dependent directives.
This issue was mentioned on a mailing list in 2006: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/186884
and from what I understood it is a bug inherited from the pack and unpack functions in Perl. The conversation ended by matz having talked to the Perl lead programmer about coordination so both languages solve this issue the same way. But then I don't know if anything happened.
___A possible solution___
http://perldoc.perl.org/perlpacktut.html#Byte-order-modifiers mentions Perl 5.9.2 supporting ">" and "<" to specify byte order for the directives that usually use the platform-dependent order. That seems like a solution! The documentation at http://search.cpan.org/~dapm/perl-5.10.1/pod/perlfunc.pod#pack may be easier to read.
___More about current status___
The docs for Ruby 1.9 still seem to miss this feature. Also the 'N' and 'V' directives operate on unsigned longs, which I think is not clear from the documentation. For all the platform-dependent formats cCsSiIlL it has pairs like "Unsigned long" and "Long" (which is then signed), but for the platform-indepedent suddenly "Long" means "Unsigned long" (applies to formats nNvV). I think that is confusing.
As explained in http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/165961 it is possible to work around this issue by unpacking with the unsigned directive and then making a function that can convert from unsigned to signed. For Array#pack it seems the function doesn't care if you input signed values, the same directive works for unsigned and signed data when packing.
I'm not sure if this is a bug or a feature request, but to be polite it made it a feature. I tested on ruby 1.8.7 (2010-01-10 patchlevel 249) [i486-linux].
----------------------------------------
http://redmine.ruby-lang.org