[#11439] comments needed for Random class — "NAKAMURA, Hiroshi" <nakahiro@...>

-----BEGIN PGP SIGNED MESSAGE-----

15 messages 2007/06/12

[#11450] Re: new method dispatch rule (matz' proposal) — David Flanagan <david@...>

This is a late response to the very long thread that started back in

17 messages 2007/06/13

[#11482] Ruby Changes Its Mind About Non-Word Characters — James Edward Gray II <james@...>

Does this look like a bug to anyone else?

10 messages 2007/06/16

[#11505] Question about the patchlevel release cycle — Sylvain Joyeux <sylvain.joyeux@...4x.org>

1.8.6 thread support was broken in bad ways. It stayed for three months

20 messages 2007/06/20
[#11512] Re: Question about the patchlevel release cycle — Urabe Shyouhei <shyouhei@...> 2007/06/20

Hi, I'm the 1.8.6 branch manager.

[#11543] Re: Apple reportedly to ship with ruby 1.8.6-p36 unless informed what to patch — James Edward Gray II <james@...>

On Jun 27, 2007, at 4:47 PM, Bill Kelly wrote:

10 messages 2007/06/27

Re: [PATCH] Another small bug fix for Ruby 1.9 and a request for clarification

From: "Florian Frank" <flori@...>
Date: 2007-06-05 23:29:35 UTC
List: ruby-core #11417
Hello,

Nobuyoshi Nakada wrote:
>> The second makes it
>> possible to build 1.9. with an installed Ruby 1.8. for bootstrapping.
>>     
>
> For cross-compiling?
That's an interesting question. I had a problem with the new syntax in 
the extmk.rb file, but now I see, that it's supposed to be called from 
miniruby. It's likely, that I had some older 1.8 miniruby laying around. 
I guess, I just got confused. The change might be useful for 
cross-compiling as well.

I usually have a hard time compiling 1.9 compared to 1.8. But I guess 
this is to be expected, because development is so much faster now than 
it used to be before the yarv merge.

I have a attached patch for rdoc-dot. The dot program of the graphviz 
package has changed it's version string output in some of the newer 2.x 
versions. Without the patch rdoc cannot draw the nice module/class 
diagrams, because it cannot figure out the required version. It might be 
useful to apply this patch to Ruby 1.8 as well (if the problem wasn't
already corrected there).

Maybe I should write a different email for this, but anyway. NARUSE Yui sent me an email about a failing JSON test. It seems the semantic for these cases have changed from Ruby 1.8.5 to Ruby 1.9:

RUBY_VERSION # => "1.8.5"
for (foo, bar) in [[1,2], [3,4]]
  [foo, bar] # => [1, 2], [3, 4]
end

for foo, bar in [[1,2], [3,4]]
  [foo, bar] # => [1, 2], [3, 4]
end

RUBY_VERSION # => "1.9.0"
for (foo, bar) in [[1,2], [3,4]]
  [foo, bar] # => [1, nil], [3, nil]
end

for foo, bar in [[1,2], [3,4]]
  [foo, bar] # => [1, 2], [3, 4]
end

I fixed my tests by always using the second form, but this could be a 
Ruby bug. Or is the semantic change intended?

-- 
Florian Frank

Attachments (1)

rdoc-dot.patch (708 Bytes, text/x-diff)
Index: lib/rdoc/options.rb
===================================================================
--- lib/rdoc/options.rb	(revision 12443)
+++ lib/rdoc/options.rb	(working copy)
@@ -550,12 +550,12 @@
     ver = nil
     IO.popen("dot -V 2>&1") do |io|
       ver = io.read
-      if ver =~ /dot\s+version(?:\s+gviz)?\s+(\d+)\.(\d+)/
+      if ver =~ /dot.*?version(?:\s+gviz)?\s+(\d+)\.(\d+)/
         ok = ($1.to_i > 1) || ($1.to_i == 1 && $2.to_i >= 8)
       end
     end
     unless ok
-      if ver =~ /^dot version/
+      if ver =~ /^dot.*?version/
         $stderr.puts "Warning: You may need dot V1.8.6 or later to use\n",
           "the --diagram option correctly. You have:\n\n   ",
           ver,

In This Thread

Prev Next