[#11396] Re: $2000 USD Reward for help fixing Segmentation Fault in GC — Brent Roman <brent@...>
Sylvain,
[#11401] Proc.== — David Flanagan <david@...>
Can anyone construct two proc objects p1 and p2, without using clone or
Hi,
Okay, anything other than the degenerate case of a proc with no body?
On Jun 4, 2007, at 22:57, David Flanagan wrote:
[#11409] Method introspection ? — "Jonas Pfenniger" <zimbatm@...>
Hello,
[#11418] currying in Ruby — David Flanagan <david@...>
I've written a little argument currying module for Procs and Methods. I
[#11431] Are there a better set of unit tests for Array? — "John Lam (CLR)" <jflam@...>
It seems like the unit tests that we have in Ruby.net were:
[#11439] comments needed for Random class — "NAKAMURA, Hiroshi" <nakahiro@...>
-----BEGIN PGP SIGNED MESSAGE-----
On 6/12/07, NAKAMURA, Hiroshi <nakahiro@sarion.co.jp> wrote:
[#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
On 6/13/07, David Flanagan <david@davidflanagan.com> wrote:
[#11457] Inclusion of bug #9376 in 1.8.6 branch — Sylvain Joyeux <sylvain.joyeux@...4x.org>
Would it be possible to include the fix for bug #9376 in 1.8.6 ? It is not
[#11462] What should this code do? — "John Lam (CLR)" <jflam@...>
Thinking about control flow these days ...
[#11472] Strange Array#transpose behavior for custom to_ary method — Daniel Berger <djberg96@...>
Ruby 1.8.6 p36
[#11481] Ancestors for Singleton classes — "Robert Dober" <robert.dober@...>
I am taking this away from ruby-talk as it contains patches.
[#11482] Ruby Changes Its Mind About Non-Word Characters — James Edward Gray II <james@...>
Does this look like a bug to anyone else?
James Edward Gray II wrote:
Hi,
On Jun 16, 2007, at 2:41 PM, Vincent Isambart wrote:
> > It is because the and サ characters are not in ISO-8859-1.
[#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
Hi, I'm the 1.8.6 branch manager.
On 6/20/07, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
> could you refer to bug #s?
Hi,
[#11533] method_missing for Enumerator — TRANS <transfire@...>
What do others think of this for 1.9+?
[#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:
Hi,
On Jun 30, 2007, at 4:51 AM, Urabe Shyouhei wrote:
Hi,
Hi,
Hi,
I haven't seen it mentioned explicitly in this thread so far, but I
[#11545] Proc initialize method not called under certain circumstances — "John Lam (CLR)" <jflam@...>
class Proc
On Fri, 29 Jun 2007 05:43:14 +0900, "John Lam (CLR)" <jflam@microsoft.com> wrote:
So, is it correct to assume that for language constructs that create built-in types like Range, Array, Hash etc that user-defined initialize methods are never called?
Re: [PATCH] Another small bug fix for Ruby 1.9 and a request for clarification
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)
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,