Actually, I don't think no leaks memory. I think eval (on a string) uses a bit of temporary space and by never moving on to the next statement, that memory is never free()d. That isn't a memory leak.

Update: Based on new information, I upgrade my guess to a memory leak in "stringy" eval on some versions of Perl on some platforms. (:

I just tried to reproduce the original problem but I couldn't. So I can't verify that there isn't a real leak. I'll try again later. Update: I don't have a platform handy that exhibits the problem. :(

But I do agree that we should avoid jumping too quickly to the "Don't do that" reply and that we can often learn interesting things from extreme and even stupid coding. (:

        - tye (but my friends call me "Tye")