[#3682] x86_64 -- warning and errors — ts <decoux@...>
4 messages
2004/11/02
[#3687] lib/ostruct.rb 1.12 - wrong commit? — Eivind Eklund <eivind@...>
The above mentioned commit makes OpenStructs into singletons, which
4 messages
2004/11/04
[#3694] Ruby 1.8.2 preview3 — Yukihiro Matsumoto <matz@...>
Hello,
10 messages
2004/11/07
[#3696] Re: Ruby 1.8.2 preview3 — Yukihiro Matsumoto <matz@...>
Hi,
5 messages
2004/11/08
[#3711] Converting nil to NULL — "Berger, Daniel" <Daniel.Berger@...>
Hi all,
5 messages
2004/11/11
[#3716] possible bug in method dictionary — Ryan Davis <ryand@...>
NOTE: to repro this bug as written, you must have RubyInline 3.1.0
6 messages
2004/11/12
[#3726] Fixnum#clone and Float#clone raise different exceptions — "David A. Black" <dblack@...>
Hi --
15 messages
2004/11/12
[#3749] Re: Fixnum#clone and Float#clone raise different exceptions
— "David A. Black" <dblack@...>
2004/11/16
Hi --
[#3751] Re: Fixnum#clone and Float#clone raise different exceptions
— Yukihiro Matsumoto <matz@...>
2004/11/16
Hi,
[#3752] Re: Fixnum#clone and Float#clone raise different exceptions
— "David A. Black" <dblack@...>
2004/11/16
Hi --
[#3819] Re: Fixnum#clone and Float#clone raise different exceptions
— "David A. Black" <dblack@...>
2004/11/25
Hi --
[#3821] Re: Fixnum#clone and Float#clone raise different exceptions
— Gavin Sinclair <gsinclair@...>
2004/11/25
On Thursday, November 25, 2004, 10:55:53 PM, David wrote:
[#3825] Re: Fixnum#clone and Float#clone raise different exceptions
— Yukihiro Matsumoto <matz@...>
2004/11/25
Hi,
[#3733] Core dump with latest Ruby from CVS — Johan Holmberg <holmberg@...>
9 messages
2004/11/15
[#3734] Re: Core dump with latest Ruby from CVS
— Yukihiro Matsumoto <matz@...>
2004/11/15
Hi,
[#3735] Re: Core dump with latest Ruby from CVS
— Ryan Davis <ryand-ruby@...>
2004/11/15
[#3756] Windows build problems (1.8.2preview3) — Nathaniel Talbott <nathaniel@...>
I'm having some very strange build problems on Windows, and thought
4 messages
2004/11/17
[#3785] The latest 1.8.2 cvs prints parse error when starting extension compiling — Yukihiro Matsumoto <matz@...>
Hi,
13 messages
2004/11/23
[#3787] Re: The latest 1.8.2 cvs prints parse error when starting extension compiling
— Johan Holmberg <holmberg@...>
2004/11/23
[#3789] Re: The latest 1.8.2 cvs prints parse error when starting extension compiling
— Yukihiro Matsumoto <matz@...>
2004/11/23
Hi,
[#3790] Re: The latest 1.8.2 cvs prints parse error when starting extension compiling
— Johan Holmberg <holmberg@...>
2004/11/23
[#3791] Re: The latest 1.8.2 cvs prints parse error when starting extension compiling
— ts <decoux@...>
2004/11/23
>>>>> "J" == Johan Holmberg <holmberg@iar.se> writes:
[#3792] Re: The latest 1.8.2 cvs prints parse error when starting extension compiling
— Yukihiro Matsumoto <matz@...>
2004/11/23
Hi,
[#3806] current ruby 1.8.2 cvs has inconsistent string handling (null char in string error) — noreply@...
Bugs item #1095, was opened at 2004-11-24 16:48
3 messages
2004/11/24
[#3809] Ruby does not compile on Red Hat Entreprise Linux 3. — noreply@...
Bugs item #1107, was opened at 2004-11-24 15:25
6 messages
2004/11/24
[#3810] Re: [ ruby-Bugs-1107 ] Ruby does not compile on Red Hat Entreprise Linux 3.
— nobu.nokada@...
2004/11/24
Hi,
[#3812] Re: [ ruby-Bugs-1107 ] Ruby does not compile on Red Hat Entreprise Linux 3.
— Johan Holmberg <holmberg@...>
2004/11/25
[#3814] Re: [ ruby-Bugs-1107 ] Ruby does not compile on Red Hat Entreprise Linux 3.
— Johan Holmberg <holmberg@...>
2004/11/25
[#3842] convert_type() uses rb_respond_to() — Florian Gro<florgro@...>
Moin!
6 messages
2004/11/28
[#3843] Re: [BUG?] convert_type() uses rb_respond_to()
— Yukihiro Matsumoto <matz@...>
2004/11/28
Hi,
[#3846] REXML::Functions.name == nil — Ryan Davis <ryand-ruby@...>
I found this oddity while running ParseTree over every .rb file in the
6 messages
2004/11/29
Re: REXML::Functions.name == nil
From:
Florian Gro<florgro@...>
Date:
2004-11-30 01:14:02 UTC
List:
ruby-core #3859
Ryan Davis wrote: > On Nov 29, 2004, at 6:30 AM, Florian Growrote: >> I'm not sure about .id as that should not be used anymore anyway, (use >> .object_id instead) but for REXML::Functions.name a workaround is to >> use Module.instance_method(:name).bind(REXML::Functions).call > > I'm not really looking for a workaround. Either I use the workaround > every time I need to get the name of a class, or we get this one > instance fixed. I don't find that very acceptable, so for now I have to > deal with the possibility of a nil name and just fake it. My point was that the workaround works generally. Use it instead of directly calling .name and you will always get the answer you expect. The above also generally works if you want to call an original, non-overridden method on an Object. Not that I'm against changing REXML::Functions.name but this is something that is frequently useful.