(Resent, with Cc: cdr-de...@common-lisp.net)
Juan Jose Garcia-Ripoll writes:
> I have been reading the CDR documents and none of them seems to
> mandate the inclusion of some feature to signal the presence of a CDR
> in an implementation. *features* right now is quite populated and I
> would not
Juan Jose Garcia-Ripoll writes:
> I have been reading the CDR documents and none of them seems to
> mandate the inclusion of some feature to signal the presence of a CDR
> in an implementation. *features* right now is quite populated and I
> would not want to fill it with further names that may c
On Fri, Aug 19, 2011 at 11:49 AM, Didier Verna wrote:
> Juan Jose Garcia-Ripoll wrote:
>
> > I have been reading the CDR documents and none of them seems to
> > mandate the inclusion of some feature to signal the presence of a CDR
> > in an implementation. *features* right now is quite populated
Juan Jose Garcia-Ripoll wrote:
> I have been reading the CDR documents and none of them seems to
> mandate the inclusion of some feature to signal the presence of a CDR
> in an implementation. *features* right now is quite populated and I
> would not want to fill it with further names that may co
> *features* right now is quite populated and I would not want
> to fill it with further names that may collide with other users's. Does
> anybody have a strong opinion or is better informed than me in this respect?
How about just using symbols with a package?
Regards,
Phil
--
Hi everybody,
I have been reading the CDR documents and none of them seems to mandate the
inclusion of some feature to signal the presence of a CDR in an
implementation. *features* right now is quite populated and I would not want
to fill it with further names that may collide with other users's.
