[#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 --

[#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

Re: Including a module twice

From: Yukihiro Matsumoto <matz@...>
Date: 2004-11-01 03:31:13 UTC
List: ruby-core #3675
Hi,

In message "Re: Including a module twice"
    on Mon, 1 Nov 2004 10:36:46 +0900, Peter <Peter.Vanbroekhoven@cs.kuleuven.ac.be> writes:

|> This small patch may improve the situation:
|
|Thanks. I wasn't sure it was this simple.

I didn't know neither.

|This has the downside that a
|module method can have more cache entries, right?

No.  The change does not affect number of cache entries.  It just
change recorded origin of a method from module to iclass.

|And search_iclass would
|then no longer be called, right?

I believe so.  I left them untouched for insurance.

							matz.

In This Thread

Prev Next