From: ts Date: 2005-10-16T23:23:37+09:00 Subject: Re: Help! define_method leaking procs... >>>>> "E" == Eric Mahurin writes: E> The above paragraph doesn't even blame ruby. This thread E> started with a real ruby program "leaking" memory. I gave a E> possible reason as that closures hold strong references to all E> variables in there scope (with a leaky example). This is really the first time that you use a language which has closure ? Guy Decoux