Re: Memory leak in ELEvaluator: approaches and alternatives

On Sep 27, 2007, at 9:37 PM  September 27, Henri Yandell wrote:

> Currently I'm avoiding the Collections refactor. Bugfixes win; though
> the worry is that people might start depending on the code as it's
> necessarily public.

Makes sense. Might also be worth considering that this code is  
probably already from an out of date Collections release -- it might  
be worth comparing it to the current release to see how much has  
changed.

Bjorn