Well, it really depends on the CDR; some of them may define a precise API in a specific package and/or don't allow multiple implementations to coexist (e.g. the MOP). Perhaps it would be better to remove any reference to the package system altogether and simply state that some CDRs might be provided by multiple coexisting implementations, and, in those cases, it is not specified how to select one of them.


On Mon, Jun 10, 2013 at 10:38 PM, Erik Huelsmann <ehuels@gmail.com> wrote:
Hi Marco,


Reading the CDR, I wonder: in paragraph 2.1.2 the authors refer to the packaging system as a means to allow co-existing multiple implementations of a CDR in one image. However, the CDR doesn't specify or even advise CDR writers to use packages nor in what way. It seems to me this CDR allows one to detect that a CDR is available in the current image, but it doesn't say *where* the programmer can find it. It feels a bit partial. Is that intended?


Regards,


Erik.






On Mon, Jun 10, 2013 at 2:27 PM, Antoniotti Marco <antoniotti.marco@disco.unimib.it> wrote:
Dear all,

following up the CDR discussion that took place aside the European Lisp Symposium in Madrid a week ago, I prepared this document that specifies how a CL environment can test for the "presence" of a given CDR.

I wanted to pass it around before submitting it formally to the CDR editors.

all the best

Marco



--
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.









-- 
Some gratuitous spam:

http://ripple.com Ripple, social credit system
http://common-lisp.net/project/armedbear ABCL, Common Lisp on the JVM
http://code.google.com/p/tapulli my Lisp open source projects
http://www.manydesigns.com/ ManyDesigns Portofino, open source model-driven Java web application framework