[#11073] segfault printing instruction sequence for iterator — <noreply@...>
Bugs item #10527, was opened at 2007-05-02 14:42
Hi,
On Thu, May 10, 2007 at 04:51:18PM +0900, Nobuyoshi Nakada wrote:
Hi,
Hi,
This seems to make valgrind much happier.
On Thu, May 17, 2007 at 11:14:35PM +0900, Paul Brannan wrote:
Hi,
Now 'a' shows up twice in the local table:
Hi,
[#11082] Understanding code: Kernel#require and blocks. — Hugh Sasse <hgs@...>
I'm trying to debug a Rails application which complains about an
On 5/4/07, Hugh Sasse <hgs@dmu.ac.uk> wrote:
On Fri, 4 May 2007, George wrote:
On Fri, May 04, 2007 at 06:18:19PM +0900, Hugh Sasse wrote:
[#11108] pattern for implementation-private constants? — David Flanagan <david@...>
Hi,
I believe there isn't a way, but I don't think it's really necessary. Just
[#11127] Bugs that can be closed — "Jano Svitok" <jan.svitok@...>
I propose closing these bugs as invalid:
[#11145] Rational comparison to 0 fails when denominator is != 1 — <noreply@...>
Bugs item #10739, was opened at 2007-05-10 22:06
Hi,
[#11169] Allow back reference with nest level in Oniguruma for Ruby again — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <wonado@...>
Remark: I posted this text in comp.lang.ruby first, but Matz told me,
Does it make sense or is it required to write this as a RCR?
[#11176] FileUtils.rm_rf misfeature? — johan556@...
Hi!
[#11210] Pathname ascend and descend inclusive parameter — TRANS <transfire@...>
I would like to suggest that Pathname#ascend and Pathname#descend
[#11234] Planning to release 1.8.6 errata — Urabe Shyouhei <shyouhei@...>
Hi all.
On 25/05/07, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
[#11252] Init_stack and ruby_init_stack fail to reinit stack (threads problem?) — <noreply@...>
Bugs item #11134, was opened at 2007-05-25 12:14
Hi,
Nobuyoshi Nakada wrote:
[#11255] ruby_1_8_6 build problem (make install-doc) — johan556@...
Hi!
[#11271] providing better support through rubyforge tracker categories — Ryan Davis <ryand-ruby@...>
I'm going to make more categories for the trackers (bugs and patches)
[#11367] BUG: next in lambda: 1.8.6 differs from 1.8.4 and 1.9.0 — David Flanagan <david@...>
A toplevel next statement in a lambda does not return a value in 1.8.6,
[#11368] $2000 USD Reward for help fixing Segmentation Fault in GC — Brent Roman <brent@...>
Hi Brent,
[ ruby-Bugs-10776 ] Class#=== bug
Bugs item #10776, was opened at 2007-05-11 14:52 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1698&aid=10776&group_id=426 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Darren Smith (flagitious) Assigned to: Nobody (None) Summary: Class#=== bug Initial Comment: Array===Array -> false Most classes return false with this usage. This problem seems like it should occur fairly common in practice if you uses case statement to determine behavior based on class. The bug occurred on: ruby 1.8.4 (2005-12-24) [powerpc-darwin7.9.0] and: ruby 1.8.5 (2006-08-25) [x86_64-freebsd6.1] (all versions tested) ---------------------------------------------------------------------- Comment By: Jano Svitok (janek) Date: 2007-05-11 15:50 Message: This is not a bug. See http://ruby-doc.org/core/classes/Module.html#M001689 for documentation on Module#=== (that is what you are calling). In fact, what this does for Modules (and therefore for classes) is check if rhs is an instance of lhs. This is true only for Class, Module (Module class is a Class, so it is also a Module), Object (Object class is an instance of Object) and Kernel (Kernel module is instance of Module class, and it has Kernel module included) - in short, it is valid only for Class.ancestors. Therefore your statement about "Most classes" is indeed true ;-) Once more, I suggest closing the bug. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1698&aid=10776&group_id=426