What was wrong with environments as in CLTL2 pp. 207-214?

[Jean-Claude Beaudoin]

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

[Marco Antoniotti]

Content preview: Excellent question. FYI, due to prodding by yours truly, and
kudos to them, Lispworks has re-introduced the API in 6.x. Cheers [...]

Content analysis details: (-0.0 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 SPF_PASS SPF: sender matches SPF record
-0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain
Archived-At: <http://permalink.gmane.org/gmane.lisp.cl-pro/753>

Excellent question.

FYI, due to prodding by yours truly, and kudos to them, Lispworks has re-introduced the API in 6.x.

Cheers

MA

Post by Jean-Claude Beaudoin
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
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.

[Jean-Claude Beaudoin]

On Fri, Dec 14, 2012 at 4:53 AM, Marco Antoniotti <

Post by Marco Antoniotti
Excellent question.

Thanks, but I was hoping for a somewhat more specific answer.

Post by Marco Antoniotti
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?

[Pascal Costanza]

Post by Marco Antoniotti
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

[Anton Vodonosov]

Content preview: Franz also has this project for "Portable compiler environments
for Common Lisp" : https://github.com/franzinc/cl-env pro mailing list //lists.common-lisp.net/cgi-bin/mailman/listinfo/pro
[...]

Content analysis details: (-100.7 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
-0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low
trust
[84.201.186.23 listed in list.dnswl.org]
-100 USER_IN_WHITELIST From: address is in the user's white-list
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(avodonosov[at]yandex.ru)
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid
Archived-At: <http://permalink.gmane.org/gmane.lisp.cl-pro/756>

Franz also has this project for "Portable compiler environments for Common Lisp" : https://github.com/franzinc/cl-env