pascal costanza

We, the CDR editors, don't know CLRFI 2 well enough to want to take the
responsibility to submit it as a CDR 2. We would welcome such a
submission, though.


Pascal

--
My website: http://p-cos.net
Common Lisp Document Repository: http://cdr.eurolisp.org
Closer to MOP & ContextL: http://common-lisp.net/project/closer/

pascal costanza

I don't see what problem this would solve, and _if_ it doesn't solve a
problem, then it's unnecessary overhead. (There will be several
"one-liners" to take care of, and unfortunately they add up.

So what problem do you think this would solve?

Pascal

--
My website: http://p-cos.net
Common Lisp Document Repository: http://cdr.eurolisp.org
Closer to MOP & ContextL: http://common-lisp.net/project/closer/

pascal costanza

Fortunately, space rarely becomes an issue on the net.

We will think about these problems when they occur. There are probably
several possible solutions, and we should choose the most appropriate
one at that stage in the future.

Anyone can submit anything. Of course, you should make sure that you
have the necessary (copy)rights to submit a document. When in doubt,
please contact us and we can try to resolve problems. Of course, the
easiest is to contact the authors of the respective documents directly.


Pascal

--
My website: http://p-cos.net
Common Lisp Document Repository: http://cdr.eurolisp.org
Closer to MOP & ContextL: http://common-lisp.net/project/closer/

pascal costanza

That's mostly up to you. You may choose to make source code part of the
submitted document, for example as an appendix, or provide it as what we
call "accompanying material." Accompanying material can, for example, be
archives of mailing lists that have led to the submitted document,
source code, presentation slides, etc. It largely depends on what you
consider essential and inessential parts of a submitted document. For
example, you can submit source code to nail the specification of some
functionality, or you can submit it to illustrate the use of some
library. The former should probably be part of the proper document, and
the latter part of accompanying material (although it could also be the
other way around in other cases, who knows .


Pascal

--
My website: http://p-cos.net
Common Lisp Document Repository: http://cdr.eurolisp.org
Closer to MOP & ContextL: http://common-lisp.net/project/closer/