Dear all,
I am currently implementing the environments interface described in section 8.5 of CLTL2 (pp. 207-214) for MKCL. It feels like a very natural extension of what was already part of the code of the Lisp-to-C compiler MKCL inherited. It feels so natural in fact that I cannot figure out why that feature has been pulled out of the final ANSI CL specification. [And I have a hell of time standing all those (declare (ignore env)) sprinkled all over the MKCL source code.]
I think that some of you reading this list were there, part of the action, during those standardization days. Maybe you could shed some light on what was wrong with this part of the spec and motivated its removal.
Cheers,
Jean-Claude Beaudoin
Excellent question.
FYI, due to prodding by yours truly, and kudos to them, Lispworks has re-introduced the API in 6.x.
Cheers
MA
On Dec 14, 2012, at 10:06 , Jean-Claude Beaudoin jean.claude.beaudoin@gmail.com wrote:
Dear all,
I am currently implementing the environments interface described in section 8.5 of CLTL2 (pp. 207-214) for MKCL. It feels like a very natural extension of what was already part of the code of the Lisp-to-C compiler MKCL inherited. It feels so natural in fact that I cannot figure out why that feature has been pulled out of the final ANSI CL specification. [And I have a hell of time standing all those (declare (ignore env)) sprinkled all over the MKCL source code.]
I think that some of you reading this list were there, part of the action, during those standardization days. Maybe you could shed some light on what was wrong with this part of the spec and motivated its removal.
Cheers,
Jean-Claude Beaudoin
pro mailing list pro@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/pro
-- Marco Antoniotti, Associate Professor tel. +39 - 02 64 48 79 01 DISCo, Università Milano Bicocca U14 2043 http://bimib.disco.unimib.it Viale Sarca 336 I-20126 Milan (MI) ITALY
Please note that I am not checking my Spam-box anymore. Please do not forward this email without asking me first.
On Fri, Dec 14, 2012 at 4:53 AM, Marco Antoniotti < antoniotti.marco@disco.unimib.it> wrote:
Excellent question.
Thanks, but I was hoping for a somewhat more specific answer.
FYI, due to prodding by yours truly, and kudos to them, Lispworks has re-introduced the API in 6.x.
This recently! And have they found significant issues while they were at it?
Franz seems to have found some and changed a few of the return values but I fail to understand why they did it in a way that is not a superset of the CLTL2 text. Any clue?
On 14 Dec 2012, at 18:12, Jean-Claude Beaudoin jean.claude.beaudoin@gmail.com wrote:
On Fri, Dec 14, 2012 at 4:53 AM, Marco Antoniotti antoniotti.marco@disco.unimib.it wrote: Excellent question.
Thanks, but I was hoping for a somewhat more specific answer.
FYI, due to prodding by yours truly, and kudos to them, Lispworks has re-introduced the API in 6.x.
This recently! And have they found significant issues while they were at it?
Franz seems to have found some and changed a few of the return values but I fail to understand why they did it in a way that is not a superset of the CLTL2 text. Any clue?
https://groups.google.com/d/msg/comp.lang.lisp/Q1yH0TtLCN4/Wy80zgLHRyYJ https://groups.google.com/d/msg/comp.lang.lisp/GQx583B6dmw/HJIVzXfOftUJ
There was also at some stage an announcement by Duane Rettig in comp.lang.lisp where the changes compared to CLtL2 were motivated, but I cannot find any links anymore…
Pascal
-- Pascal Costanza
Franz also has this project for "Portable compiler environments for Common Lisp" : https://github.com/franzinc/cl-env
-
Anton Vodonosov -
Jean-Claude Beaudoin -
Marco Antoniotti -
Pascal Costanza