implementation package CCL

Hi,

I found a curious error right now trying to create a package with name ccl:

CL-USER 1 > (defpackage #:ccl
(:use #:cl))

Error: Trying to redefine the implementation package CCL
1 (continue) Delete the existing CCL package
2 (abort) Return to level 0.
3 Return to top loop level 0.

Type :b for backtrace or :c <option number> to proceed.
Type :bug-form "<subject>" for a bug report template or :? for other options.

CL-USER 2 : 1 >

While trying to access the exported symbols for this package, (in listener completion) I've found the ccl package is an alias for system.

Any other hidden "implementation packages" whose names we can't use?

Br,

/Alexey

Re: implementation package CCL

(list-all-packages) and look both at package names and nicknames. 

- nick

> On 6 Oct 2017, at 13:07, Alexey Veretennikov <txm.fourier@gmail.com> wrote:
> 
> Hi,
> 
> I found a curious error right now trying to create a package with name ccl:
> 
> CL-USER 1 > (defpackage #:ccl
>               (:use #:cl))
> 
> Error: Trying to redefine the implementation package CCL
>   1 (continue) Delete the existing CCL package
>   2 (abort) Return to level 0.
>   3 Return to top loop level 0.
> 
> Type :b for backtrace or :c <option number> to proceed.
> Type :bug-form "<subject>" for a bug report template or :? for other options.              
> 
> CL-USER 2 : 1 > 
> 
> While trying to access the exported symbols for this package, (in listener completion) I've found the ccl package is an alias for system.
> 
> Any other hidden "implementation packages" whose names we can't use?
> 
> Br,
> /Alexey


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: implementation package CCL

On 06.10.17 13:40, Nick Levine wrote:

>> I found a curious error right now trying to create a package with name ccl:
>>
>> CL-USER 1 > (defpackage #:ccl
>>                (:use #:cl))
>>
I think I run into this like long time ago when I noted that #+ccl does 
not necesarily denotes macintosh common lisp.

If all lisps have nicks of 3 letters and the second and third letter is 
C for common on L for lisp than clashes betwen
coral common lisp
and
cambridge common lisp
become likely.

regards

Karsten

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html