[#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: RFE: Kernel#set_trace_func
From:
Florian Groß <florgro@...>
Date:
2004-11-27 23:45:01 UTC
List:
ruby-core #3840
trans. (T. Onoma) wrote: > On Saturday 27 November 2004 06:26 pm, Florian Groß wrote: > | Would it be possible to let set_trace_func() return the trace func that > | was set before the current one gets stored? This would be very useful > | when you have a temporary trace func that will go away quickly. I'd find > | this particularly useful for letting Binding.of_caller and Tracer > | coexist peacefully, but I'm pretty sure there are a lot more use cases. > > Would a stack be even better? Yes, but I'm trying to keep the changes as small as possible for increasing the chance of it getting made. If your suggestion were to be implemented that would be even better, but I'm also happy with the original proposal.