On Jul 26, 2006, at 10:10 AM, Marco Monteiro wrote:
> Matthew Astley wrote:
>> | All the symbols presented in this document are available as
>> external symbols
>> | in a package named or nicknamed SSC.
>>
>> If the package's primary name is SSC, how is the code to determine
>> which SSC implementation it is using? Is there any reason not to say
>> that SSC shall be a nickname?
>
> I don't understand what is the problem. Note that if some code needs to
> determine which SSC implementation it is using, then SSC has failed. At
> most, it might be interesting to know which CL implementation you are
> using, and that is easy.
For that I would suggest CL-ENVIRONMENT from the CLOCC (shameless plug
:) )
As for the nicknaming of the package, there is a rationale for making
SSC a nickname. I know this is debatable, but the following scheme
should be capable of handling most implementations (although there is
no ANSI guarantee)
(defpackage "COM.IMPLEMENTATION-X.SSC" (:use "CL" "WHATEVER")
(:nicknames "SSC")
...
)
In this case you can detect (again, in most implementations) whether
you are trying to load two versions of the SSC library. At the same
time your code remains portable.
Cheers
--
Marcoxa
_______________________________________________
Gardeners mailing list
[email protected]
http://www.lispniks.com/mailman/listinfo/gardeners
