Good question! I ran a test on my Linux box and it seems to work there,
anyway. The test repeatedly caused the cache to dump items by loading more
components that it could handle. After a few iterations the process size
maxed out at 6 MB. So it looks like the subroutines do get freed.
If I get around to it at some point I'll cleanup and post the test program.
Jon
At 01:46 PM 1/24/00 -0800, Perrin Harkins wrote:
>On Sun, 23 Jan 2000, Jonathan Swartz wrote:
>> - New in-memory code cache keeps track of component usage, and
>> discards the most infrequently used components as needed. You can
>> specify the cache size with interp->max_code_cache_size.
>
>This sounds cool, but does it work, i.e. when you undef a sub reference,
>does the memory really get released and reused?
>- Perrin
>
