Yeah, I'm not really sure how I think the problem would be ideally solved. It would just be nice for an interactive programming environment to be able to recover from all exceptions that happen at a higher level than the VM itself.
On Jan 10, 12:20 pm, "Christian Vest Hansen" <karmazi...@gmail.com> wrote: > I don't think it is possible to define a way to deal with heap > saturation that is general enough to cover all programs written in > Clojure, and therefor I don't think this is something that the Clojure > runtime should deal with at all. > > Personally, I only know of two ways to handle OutOfMemoryErrors: 1) > let the program blow up and hope someone notices or 2) look at your > body, pick the limb you are least likely to be needing pretty soon and > cut it off (aka. free some memory) and _then_ yell for help through > some hopefully reliable channel. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
