OK?
-- Fernando D. Mato Mira Real-Time SW Eng & Networking Advanced Systems Engineering Division CSEM Jaquet-Droz 1 email: matomira AT acm DOT org CH-2007 Neuchatel tel: +41 (32) 720-5157 Switzerland FAX: +41 (32) 720-5720 www.csem.ch www.vrai.com ligwww.epfl.ch/matomira.html
it seems counterintuitive and random, as in "project code name".
what is it _really_ supposed to identify?
#:Erik
I just want something to abbreviate any CMUCL offspring, in case
I have to start doing #+(or :cmu :sbcl).
Note that this is something someone might want use for its own
abbreviation purposes. It's not supposed
to be predefined, as older CMUCL releases won't have it.
And one normally should do (delete :pittsburgh *features*) after being
done, so as not to leave unnecessary crud around.
Fernando> Erik Naggum wrote:
>> * "Fernando D. Mato Mira" <mato...@iname.com>
>> | #+(or :cmu :sbcl)
>> | (cl:eval-when (load eval compile)
>> | (cl:pushnew :pittsburgh cl:*features*))
>> |
>> | OK?
>>
>> it seems counterintuitive and random, as in "project code name".
>>
>> what is it _really_ supposed to identify?
Fernando> I just want something to abbreviate any CMUCL offspring, in case
Fernando> I have to start doing #+(or :cmu :sbcl).
Why not use something a bit more intuitive like :cmu-or-sbcl instead
of some totally random :pittsburgh?
Ray
> Why not use something a bit more intuitive like :cmu-or-sbcl instead
> of some totally random :pittsburgh?
Better would be CMU-OFFSPRING or something (there might be others...)
--tim
> >>>>> "Fernando" == Fernando D Mato Mira <mato...@iname.com> writes:
>
> Fernando> Erik Naggum wrote:
> >> * "Fernando D. Mato Mira" <mato...@iname.com>
> >> | #+(or :cmu :sbcl)
> >> | (cl:eval-when (load eval compile)
> >> | (cl:pushnew :pittsburgh cl:*features*))
> >> |
> >> | OK?
> >>
> >> it seems counterintuitive and random, as in "project code name".
> >>
> >> what is it _really_ supposed to identify?
>
> Fernando> I just want something to abbreviate any CMUCL offspring, in case
> Fernando> I have to start doing #+(or :cmu :sbcl).
>
> Why not use something a bit more intuitive like :cmu-or-sbcl instead
> of some totally random :pittsburgh?
Not just for those 2. For any CMUCL forks that may ever happen.
:Anything better than :cmu-offspring?
:cmucl ?
[Random??]