CDR-14 and optional modules
Burton Samograd
busfactor1 at icloud.com
Sat Jun 1 20:46:13 UTC 2019
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 at 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 at 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 bye
>> Michael Raskin
>>
>>
>>
>
> --
> Marco Antoniotti
>
>
>
More information about the pro
mailing list