jack-rack-devel

[jack-rack-devel] Garbage Collection

[Leslie P. P. <les...@gm...>]

Hello everyone,

how about fitting the Boehm-Weiser Garbage Collector into JACK Rack?
The code is convoluted enough right now, and it would ease the
situation a little bit.

And manual memory management is an anachronism anyway today, although
most C programmers don't want to realize it.

  Leslie

Re: [jack-rack-devel] Garbage Collection

[Adam S. <at...@of...>]

"Leslie P. Polzer" <les...@gm...> writes:

> how about fitting the Boehm-Weiser Garbage Collector into JACK Rack?
> The code is convoluted enough right now, and it would ease the
> situation a little bit.

I'm not especially opposed to the idea -- I dislike manual memory
management too -- but JACK Rack's memory allocation patterns are
pretty straightforward (outside of the GTK bits, which are handled by
GTK's refcounting allocator anyway), and last time I checked with
Valgrind it didn't seem to be suffering from memory leaks or other
MM problems, so I'm inclined to leave it on the "if it ain't broke"
principle.

It would require going through the code and dividing the current
allocations and frees between things that are actually getting passed
to GTK (and thus can't be GCd) and things that aren't (and thus can),
but otherwise should be fairly straightforward to try out.

-- 
Adam Sampson <at...@of...>                         <http://offog.org/>