[#11073] segfault printing instruction sequence for iterator — <noreply@...>

Bugs item #10527, was opened at 2007-05-02 14:42

14 messages 2007/05/02
[#11142] Re: [ ruby-Bugs-10527 ] segfault printing instruction sequence for iterator — Nobuyoshi Nakada <nobu@...> 2007/05/10

Hi,

[#11188] Re: [ ruby-Bugs-10527 ] segfault printing instruction sequence for iterator — Paul Brannan <pbrannan@...> 2007/05/16

On Thu, May 10, 2007 at 04:51:18PM +0900, Nobuyoshi Nakada wrote:

[#11234] Planning to release 1.8.6 errata — Urabe Shyouhei <shyouhei@...>

Hi all.

17 messages 2007/05/25

Re: Garbage collection of Symbols in future release?

From: Sven Suska <sven716rc@...>
Date: 2007-05-17 06:40:53 UTC
List: ruby-core #11191
Hello,

Yukihiro Matsumoto schrieb:

>In message "Re: Garbage collection of Symbols in future release?"
>    on Thu, 17 May 2007 06:20:47 +0900, Sven Suska <sven716rc@suska.org> writes:
>
>|Does the feature list of Ruby 1.9 include
>|the garbage collection of Symbols?
>
>No.  It's pretty difficult to detect symbols that can be removed
>safely.  If anyone has good idea, I'd love to hear.
>
>							matz.
>  
>
O, I thought it was simple. But I am not a core programmer.

My idea was to go through every (class, gobal, local) variable
in the whole system and mark all Symbols in the table that are still used.
Then regenerate the table with only these Symbols.

Do this only, if the total number of Symbols exceeds a limit.
Then the amortized time should hardly be noticeable.

Where does this not match with reality?

Regards,
Sven

In This Thread

Prev Next