A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg00657.html below:

Re: Help sought understanding shorthands wrt modules/packages

Richard Stallman <rms@gnu.org> writes:

> [[[ To any NSA and FBI agents reading my email: please consider    ]]]


> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>   > I don't agree.  Symbols are at the heart of Lisp.  Changing their
>   > semantics is a big deal, and as soon as that features is in, it will be
>   > used.
>
> The shorthands feature is already installed, but it doesn't change the
> sematics of symbols.

I don't agree.  Before shorthands, a symbol had one name, after, it can


have many.

This is incorrect. You're confusing the text manifestation of a symbol in a Lisp form before it is read (as in CL:READ) with the symbol itself, which has only one name. This didn't and couldn't change with shorthands. 

Deciding to use it not use a shorthand is no different from deciding to use or not use package qualification for a symbol in CL packages.

Neither changes the name of a symbol, just the manifestation is different. If you force them to be the same thing, then no namespacing symbol is possible at all

If you conflate symbol name and symbol designation/manifestation in source files , you'll have problems implementing any package system (CL, shorthands, whatever) and you confuse people trying to understand any Lisp package system, i.e. you confuse this discussion. Let's try to avoid that :)


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4