On Tue, Jul 9, 2013 at 1:22 AM, Mikera <mike.r.anderson...@gmail.com> wrote:
> 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. > Ah yes, I remember that post. Here is my take: It would be easier to do this first as an interpreter. There's just fewer problems to solve that way. Most importantly, its possible to bypass all JVM-implementation-detail-related issues, at least for pure Clojure code. For instance, in an interpreter, deftype/defrecord don't need to generate java classes. My idea is a little different though. An interpretive environment can do things that a compiled one cannot. For instance, runtime errors can return literal code snippets, rather than class names / line numbers. Or, you can a la carte assign new interpretations to functions and classes you do not control. You can also change the semantics of the language itself, to support things like partial evaluation. -- -- 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.
