[#5563] Non-overridable and non-redefinable methods — Eric Mahurin <eric_mahurin@...>

Lately, I've been thinking about the future of ruby

44 messages 2005/08/19
[#5564] Re: Non-overridable and non-redefinable methods — Austin Ziegler <halostatue@...> 2005/08/19

On 8/19/05, Eric Mahurin <eric_mahurin@yahoo.com> wrote:

[#5571] Re: Non-overridable and non-redefinable methods — Eric Mahurin <eric_mahurin@...> 2005/08/19

--- Austin Ziegler <halostatue@gmail.com> wrote:

[#5574] Re: Non-overridable and non-redefinable methods — TRANS <transfire@...> 2005/08/20

Just wanted to add a few things.

[#5581] Re: Non-overridable and non-redefinable methods — Austin Ziegler <halostatue@...> 2005/08/20

On 8/19/05, TRANS <transfire@gmail.com> wrote:

[#5583] Re: Non-overridable and non-redefinable methods — "David A. Black" <dblack@...> 2005/08/20

Hi --

[#5585] Re: Non-overridable and non-redefinable methods — Eric Mahurin <eric_mahurin@...> 2005/08/20

--- "David A. Black" <dblack@wobblini.net> wrote:

[#5609] Pathname#walk for traversing path nodes (patch) — ES <ruby-ml@...>

Here is a small addition to Pathname against 1.9, probably suited

20 messages 2005/08/22

Minor bug: recursive Thread.current[:__inspect_key__]?

From: =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...>
Date: 2005-08-07 09:35:53 UTC
List: ruby-core #5533
Moin.

Here is some odd border case behavior I have stumbled upon:

> irb(main):001:0> x = []; x << x; Thread.current[:__inspect_key__] = x
> => [[...], 23694880]                                                 
> irb(main):002:0> x.size                                              
> => 1                                                                 

It seems pretty harmless, but is probably best fixed anyway.

Also, it is possible to freeze the inspect key array which will then 
result in an exception from Object#inspect -- I could however not cause 
a segfault so it is probably safe.

Regards,
Florian Gross


In This Thread

Prev Next