> How do long-running systems like > Erlang handle this problem? iiuc, erlang doesn't have transactions so it is a different situation. when you redefine a function, the next time the (standard approach to writing erlang actors) tail call goes back into the function it will be actually going into the new definition. so of course that limits exactly what can be changed. and it only allows for one version to be running at a time so anything depending on it would have to be upgraded somehow simultaneously? (well, erlang systems tend to be written to handle errors well i guess so maybe you can step-wise upgrade bits and pieces until it is all working again.)
--~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
