Context specific Interlisp symbols? #2575
-
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
|
Some Interlisp applications and systems use namespace-ish prefixes in symbol names such as However, something like |
Beta Was this translation helpful? Give feedback.
-
|
I don't have a general answer to context specific symbols, but in this case it would be OK to define LT as a function, as that won't interfere with its CLISP definition. When you do |
Beta Was this translation helpful? Give feedback.
-
|
It seems that the prefixed-names are just using packages without using packages. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the help! I was able to simply use ED(LT FNS) to create a new definition. All good now. |
Beta Was this translation helpful? Give feedback.
-
|
You could also have done |
Beta Was this translation helpful? Give feedback.

I don't have a general answer to context specific symbols, but in this case it would be OK to define LT as a function, as that won't interfere with its CLISP definition. When you do
ED(LT)you're asking it to edit some definition, and since it has a property listEDgoes ahead with that. You can do ED(LT FNS) and since it does not (yet) have a FNS definition it will ask if you want a LAMBDA or NLAMBDA dummy definition. Go ahead and give it the expected definition. Once it has both a FNS and a PROPERTY-LIST definition, if you don't ask to edit a particular one (e.g., you do ED(LT) rather than ED(LT FNS)) it will ask which definition to edit. Type enough to disambiguate the types presented.