2013/7/9 Mikera <mike.r.anderson...@gmail.com>: > My post "The Environment as a Value" might be of interest to you. > > https://groups.google.com/forum/#!searchin/clojure-dev/immutable$20environment/clojure-dev/S8BawG7nzJA/qfCd7hn67aoJ > > It contains a lot of similar ideas. An important point is that you don't > necessarily need an interpreter to get the benefits of an immutable isolated > environment: this can still be fully compiled.
Modulo side effects such as: - classloading of new fns : not a real problem, but the limit of the PermGen maybe - Protocols / Types recompilation: this may be a problem ? (unless the whole compilation happens in a different classloader ?) > > In terms of state mutations, they key point is that you need some form of > dependency graph: if you update one var, this can then trigger a > recompilation of dependent vars to get you to a consistent new state. This > also solves the problem of circular references as a by-product. > > It was a cool idea, but nobody seemed very interested at the time :-( > > > On Tuesday, 9 July 2013 00:55:18 UTC+1, kovasb wrote: >> >> I believe a reify-able clojure interpreter would be useful and >> interesting. >> >> For instance, for debugging, partial evaluation, environment capture / >> manipulation, and a variety of tasks that currently require resetting the >> environment just to see the behavior of code. >> >> I imagine this being mostly useful at the repl, for exploring the behavior >> of programs, and for temporarily changing the meaning of pieces of programs >> without digging into source code. >> >> Anyone with me? Does such a thing already exist? >> >> My basic design idea is to have a protocol IClojure that implements the >> primitives necessary to bootstrap clojure.core. >> >> IClojure would be implemented by a concrete datatype. >> >> State mutations would correspond to returning new instances of the >> datatype. >> >> Basically, this would be a clojure interpreter as immutable data. So you >> can fabricate an interpreter with the state that you need, and keep reusing >> it as you debug your other code. >> >> One aspect I'm not clear on is platform isolation. >> >> > -- > -- > 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 > Note that posts from new members are moderated - please be patient with your > first post. > 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 > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- 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 Note that posts from new members are moderated - please be patient with your first post. 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
