Interlisp
Defpackage is in package XEROX-COMMON-LISP instead of LISP
Describe the bug DEFPACKAGE is defined in package XEROX-COMMON-LISP instead of LISP
To Reproduce 2/39> (symbol-package 'defpackage) #<Package XEROX-COMMON-LISP> 2/40> (symbol-package 'in-package) #<Package LISP>
Expected behavior All the other package commands are in LISP, and I would expect defpackage to be there too.
Screenshots
Context (please complete the following information):
- OS: observed in both Mac and Online
- IL:MAKESYSDATE: [22-Apr-2024 02:03:41 ]
Additional context All of this changes in CLtL2, anyway, when LISP becomes COMMON-LISP, so maybe not worth fixing now.
Huh. Github renders the hashtag-lessthan symbols as blanks, so I've replaced that section of the issue with a screenshot instead of a dribble.
I try to put dribble output inside a quote-quote-quote code block so it doesn't interpret the hash-lessthan, or anything else, as markdown.
Note that symbols which are exported from CL (or LISP) don't need to have it as their home package. So CL doesn't require that (symbol-package 'cl:car) is the CL package.
I don't know whether this is the case here, but if it is then it isn't a bug.
it seems like some features that were not final were put in the xcl package to start out. Not all cleanup proposals were adopted:
see proposal for defpackage CLHS: Issue DEFPACKAGE Writeup (interlisp.org) https://interlisp.org/clhs/Issues/iss108_w.htm
and email discussion (Visual Studio Code seems to display this): parcftp-cl/cl/cleanup/old-mail/defpackage.mail at main · masinter/parcftp-cl (github.com) https://github.com/masinter/parcftp-cl/blob/main/cl/cleanup/old-mail/defpackage.mail
On Sat, Apr 27, 2024 at 11:54 AM Tim Bradshaw @.***> wrote:
Note that symbols which are exported from CL (or LISP) don't need to have it as their home package. So CL doesn't require that (symbol-package 'cl:car) is the CL package.
I don't know whether this is the case here, but if it is then it isn't a bug.
— Reply to this email directly, view it on GitHub https://github.com/Interlisp/medley/issues/1684#issuecomment-2081149012, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAIQTK7BOYBXZ3IWOMJTTNLY7PX6JAVCNFSM6AAAAABG4FWJIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGE2DSMBRGI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- https://LarryMasinter.net https://interlisp.org
It isn’t the case here. If you create an Exec and choose “Common Lisp” as the exec type, DEFPACKAGE isn’t available to you. The other package commands work ‘cause they’re defined from LISP, but DEFPACKAGE is in XCL.
It’s not a common bug to get hit by, since it requires one to be in a package that doesn’t inherit from XCL. It requires one to do a DEFPACKAGE that doesn’t inherit from XCL, then an IN-PACKAGE into that package, and then attempt another DEFPACKAGE. If the system starts out by doing all the DEFPACKAGE’s and then IN-PACKAGE things work just fine.
On Apr 27, 2024, at 1:54 PM, Tim Bradshaw @.***> wrote:
Note that symbols which are exported from CL (or LISP) don't need to have it as their home package. So CL doesn't require that (symbol-package 'cl:car) is the CL package. I don't know whether this is the case here, but if it is then it isn't a bug. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
