<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hi
<div class=""><br class="">
</div>
<div class="">I looked at the proposal.</div>
<div class=""><br class="">
</div>
<div class="">I agree it would be useful, but I have two concerns.</div>
<div class=""><br class="">
</div>
<div class="">
<ul class="">
<li class="">The proposal requires the presence of a <font face="Courier New" class="">
<span style="font-style: normal;" class="">CDR-NN</span></font> package. Such a proposal should be made separately. FTTB if
<font face="Courier New" class=""><span style="font-style: normal;" class="">CDR-14</span></font> is used, only the
<font face="Courier New" class=""><span style="font-style: normal;" class="">CDR-NN</span></font> feature should be provided. I would be in favor of a new CDR stating that a
<font face="Courier New" class=""><span style="font-style: normal;" class="">CDR-XX</span></font> nickname could be added to a package implementing a given feature.</li><li class="">The proposal as is may not be portably implemented by a third party without resorting to implementation support which may or may not be there. The problematic operators are
<font face="Courier New" class=""><span style="font-style: normal;" class="">WITH-PARENT-ENVIRONMENT</span></font> and
<font face="Courier New" class=""><span style="font-style: normal;" class="">ENVIRONMENT-ENTRY-NAMES</span></font>. Do you see any way to provide it in a simple (read: non SBCL) way?</li></ul>
</div>
<div class=""><br class="">
</div>
<div class="">Finally, <font face="Courier New" class=""><span style="font-style: normal;" class="">COPY-ENVIRONMENT</span></font> may and
<font face="Courier New" class=""><span style="font-style: normal;" class="">LEXICAL-ENVIRONMENT</span></font> also be problematic.</div>
<div class=""><br class="">
</div>
<div class="">cheers</div>
<div class=""><br class="">
</div>
<div class="">Marco Antoniotti</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<br class="">
<blockquote type="cite" class="">On Apr 25, 2019, at 16:47 , Michael Raskin <<a href="mailto:38a938c2@rambler.ru" class="">38a938c2@rambler.ru</a>> wrote:<br class="">
<br class="">
Hello.<br class="">
I want to try to do something about portability of universally<br class="">
present features, given that stndard revisions are extremely unlikely,<br class="">
and CDR process seems to be the best way to obtain a stable ID for some <br class="">
version of description.<br class="">
<br class="">
As automatic code processing is a large part of Common Lisp <br class="">
identity as it is presented, and there is a small and easy to define <br class="">
chunk of functionality that is missing, I am preparing a CDR on portable<br class="">
code walking support.<br class="">
<br class="">
Before I formally submit a CDR proposal, I want to try to get<br class="">
some feedback. The current version of the writeup I have is at:<br class="">
<a href="https://gitlab.common-lisp.net/mraskin/cdr-walkability/blob/master/walkability.txt" class="">https://gitlab.common-lisp.net/mraskin/cdr-walkability/blob/master/walkability.txt</a><br class="">
<br class="">
Please comment on that proposal, here or via issues or maybe<br class="">
even merge requests. I will announce the link to the discussion in the<br class="">
ELS mailing list (as ELS conference seems to be the closest <br class="">
approximation to community discussion we have).<br class="">
<br class="">
I considered including Trucler API as an option, but currently<br class="">
I doubt I am able to do it well: mixing a coherent API with multiple <br class="">
optional additions that are useful even as single functions is a harder<br class="">
task. I want to start somewhere.<br class="">
<br class="">
Separately, if someone has some proposals on how to make CDR<br class="">
process used more — or matter more, please share. Probably on cdr-devel<br class="">
https://mailman.common-lisp.net/listinfo/cdr-devel<br class="">
<br class="">
Thank you, goodbye<br class="">
Michael Raskin<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
</blockquote>
<br class="">
<div class="">--<br class="">
Marco Antoniotti, Associate Professor<span class="Apple-tab-span" style="white-space:pre">
</span>tel.<span class="Apple-tab-span" style="white-space:pre"> </span>+39 - 02 64 48 79 01<br class="">
DISCo, Università Milano Bicocca U14 2043<span class="Apple-tab-span" style="white-space:pre">
</span><a href="http://bimib.disco.unimib.it" class="">http://bimib.disco.unimib.it</a><br class="">
Viale Sarca 336<br class="">
I-20126 Milan (MI) ITALY<br class="">
<br class="">
Please check: http://cdac2019.lakecomoschool.org<br class="">
Please check: http://troncopackage.org<br class="">
Please check: https://www.frontiersin.org/research-topics/7394/network-bioscience<br class="">
<br class="">
Please note that I am not checking my Spam-box anymore.<br class="">
Please do not forward this email without asking me first (cum grano salis).<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
</div>
<br class="">
</div>
</body>
</html>