Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Hi,
>No problem. Is there a simple workaround (other than explicitly
>calling free before rb_raise), such as registering the address with the
>GC? One would have to wrap it in a VALUE it seems, which isn't
>great...
There's no way for Ruby GC to handle non-VALUE data. The only
solution I can think of is moving to Boehm GC, which might be an
overkill.
matz.
Won't ALLOCA_N work for this, or am I not following?
···
In message "Re: rb_raise and memory" > on Thu, 10 Mar 2005 08:25:49 +0900, Nikolai Weibull <mailing-lists.ruby-talk@rawuncut.elitemail.org> writes:
George Ogata wrote:
Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Hi,
No problem. Is there a simple workaround (other than explicitly
calling free before rb_raise), such as registering the address with the
GC? One would have to wrap it in a VALUE it seems, which isn't
great...
There's no way for Ruby GC to handle non-VALUE data. The only
solution I can think of is moving to Boehm GC, which might be an
overkill.
matz.
Won't ALLOCA_N work for this, or am I not following?
alloca memory is deallocated at the end of the scope, which is not a good thing if you expect to use it later...
-garrett
···
In message "Re: rb_raise and memory" >> on Thu, 10 Mar 2005 08:25:49 +0900, Nikolai Weibull <mailing-lists.ruby-talk@rawuncut.elitemail.org> writes:
Garrett Rooney <rooneg@electricjellyfish.net> writes:
alloca memory is deallocated at the end of the scope, which is not a
good thing if you expect to use it later...
Right, I was thinking of a different situation. Sorry.
George Ogata wrote:
Yukihiro Matsumoto <matz@ruby-lang.org> writes:
Hi,
No problem. Is there a simple workaround (other than explicitly
calling free before rb_raise), such as registering the address with the
GC? One would have to wrap it in a VALUE it seems, which isn't
great...
There's no way for Ruby GC to handle non-VALUE data. The only
solution I can think of is moving to Boehm GC, which might be an
overkill.
matz.
Won't ALLOCA_N work for this, or am I not following?
alloca memory is deallocated at the end of the scope, which is not a
good thing if you expect to use it later...
Well, there's an argument to be made that any memory that's to be used
later should be either invalidated by the exception or released somewhere
else anyway.
-garrett
E
···
On Thu, March 10, 2005 5:51 pm, Garrett Rooney said:
In message "Re: rb_raise and memory" >>> on Thu, 10 Mar 2005 08:25:49 +0900, Nikolai Weibull >>> <mailing-lists.ruby-talk@rawuncut.elitemail.org> writes: