-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/30/2011 01:50 PM, Andre van Tonder wrote: > On Fri, 30 Sep 2011, Alaric Snell-Pym wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 09/29/2011 05:25 PM, Andre van Tonder wrote: >> >>> On a system that that invokes a compiler on the argument of EVAL, the >>> compiler >>> may depend on the textual representation of the code '(cons 1 2). It >>> may even >>> do certain optimizations and rewritings based on the textual >>> representation. >>> Again, having procedure objects in here confuses levels and can cause >>> problems >>> for such a compiler. >> >> Does it really? Can anyone point to an implementation of EVAL that can't >> cope with this? > > I don't think Larceny's eval can cope with this. >
Why is that? How does it work? What's the architectural tradeoff they've made? MORE DATA :-) ABS - -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6Fu88ACgkQRgz/WHNxCGo9tgCcCj/WYDsNzD/U1/RSuFiivpTL 5AsAn3loIyyWfV5TjwFnPW3AOIB8PzcQ =dJvs -----END PGP SIGNATURE----- _______________________________________________ Scheme-reports mailing list [email protected] http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports
