> This could be a real problem for Clojure. I can think of other > techniques that could easily result in the creation a large number of > anonymous functions that ought to get gc'd after a few ms but > permanently increase memory usage by a significant amount. I don't > know the JVM very well at all. Are there any ways around this? Are > techniques that generate a lot of short-lived functions just not > practical in Clojure?
It seems that anonymous functions in general might be a sort of anti- pattern. Beyond deeply-nested applications like GP, there's the case of any long-running process e.g. pretty much any server application. The growth might be slower, but sooner or later that server is going to accumulate too many... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
