Hi
if you don’t load code that implements a feature you wouldn’t be able to push a feature onto the *FEATURES* list.
That is, unless you are a jerk :) :) :) and push stuff onto the *FEATURES* list just for the heck of it, or as a, I’d say tasteless, joke :) :) :)
Cheers
MA
On May 12, 2019, at 22:04 , Michael Raskin 38a938c2@rambler.ru wrote:
Hello I look at CDR-14 that says about putting :CDR-NN symbols into*features* if implementation purports to implement a CDR. What is the recommended behaviour in the case when the implementation provides a loadable module to support a CDR? Should the feature be always present or only appear when the module is loaded? What are the opinions?
Thank you, good byeMichael Raskin
-- Marco Antoniotti
Feature this.
Where's my cocaine?
See They’re fucking with my copy paste.
I’m not paranoid And you guys are dead too.
Bye friends
Burton
Sent from my iPhone
On May 26, 2019, at 2:17 AM, Marco Antoniotti marcoxa@cs.nyu.edu wrote:
Hi
if you don’t load code that implements a feature you wouldn’t be able to push a feature onto the *FEATURES* list.
That is, unless you are a jerk :) :) :) and push stuff onto the *FEATURES* list just for the heck of it, or as a, I’d say tasteless, joke :) :) :)
Cheers
MA
On May 12, 2019, at 22:04 , Michael Raskin 38a938c2@rambler.ru wrote:
Hello I look at CDR-14 that says about putting :CDR-NN symbols into*features* if implementation purports to implement a CDR. What is the recommended behaviour in the case when the implementation provides a loadable module to support a CDR? Should the feature be always present or only appear when the module is loaded? What are the opinions?
Thank you, good byeMichael Raskin
-- Marco Antoniotti
Just kidding the cops stole it.
And killed my favourite one.
She was super hot.
And full of blood.
Burton
Sent from my iPhone
On Jun 1, 2019, at 2:46 PM, Burton Samograd busfactor1@icloud.com wrote:
Feature this.
Where's my cocaine?
See They’re fucking with my copy paste.
I’m not paranoid And you guys are dead too.
Bye friends
Burton
Sent from my iPhone
On May 26, 2019, at 2:17 AM, Marco Antoniotti marcoxa@cs.nyu.edu wrote:
Hi
if you don’t load code that implements a feature you wouldn’t be able to push a feature onto the *FEATURES* list.
That is, unless you are a jerk :) :) :) and push stuff onto the *FEATURES* list just for the heck of it, or as a, I’d say tasteless, joke :) :) :)
Cheers
MA
On May 12, 2019, at 22:04 , Michael Raskin 38a938c2@rambler.ru wrote:
Hello I look at CDR-14 that says about putting :CDR-NN symbols into*features* if implementation purports to implement a CDR. What is the recommended behaviour in the case when the implementation provides a loadable module to support a CDR? Should the feature be always present or only appear when the module is loaded? What are the opinions?
Thank you, good byeMichael Raskin
-- Marco Antoniotti
Did you guys get this?
Can you see the codes?
Decypt.
This is important.
Maybe.
Burton
Sent from my iPhone
Begin forwarded message:
From: Marco Antoniotti marcoxa@cs.nyu.edu Date: May 26, 2019 at 2:17:47 AM MDT To: cdr-discuss@common-lisp.net Cc: pro@common-lisp.net Subject: Re: CDR-14 and optional modules Reply-To: marco.antoniotti@unimib.it, Discussion list for Common Lisp professionals pro@common-lisp.net
Hi
if you don’t load code that implements a feature you wouldn’t be able to push a feature onto the *FEATURES* list.
That is, unless you are a jerk :) :) :) and push stuff onto the *FEATURES* list just for the heck of it, or as a, I’d say tasteless, joke :) :) :)
Cheers
MA
On May 12, 2019, at 22:04 , Michael Raskin 38a938c2@rambler.ru wrote:
Hello I look at CDR-14 that says about putting :CDR-NN symbols into*features* if implementation purports to implement a CDR. What is the recommended behaviour in the case when the implementation provides a loadable module to support a CDR? Should the feature be always present or only appear when the module is loaded? What are the opinions?
Thank you, good byeMichael Raskin
-- Marco Antoniotti
-
Burton Samograd -
Burton Samograd＠gmail -
Marco Antoniotti