Re: Why :USE sucks in the Common Lisp package system

[Andreas Schwab <schwab@linux-m68k.org>]

On Mai 09 2020, Andrea Corallo wrote:

> "Michał \"phoe\" Herda" <phoe@disroot.org> writes:
>
>> While I'm no emacs programmer (this is my first post here!), I think
>> that a package system with PLNs could work for elisp as a tool for
>> symbol namespacing, as long as it is clear that elisp programmers know
>> not to repeat the mistake from the CL ecosystem and only use :USE for
>> packages that either do not change (in our case, it's the COMMON-LISP
>> package), or a package that changes but is the only used package (and
>> therefore has nothing to conflict with), or a combination of packages
>> that do not change and we have full control over so we can manually see
>> and resolve the symbol conflicts as they arise. And then, we locally
>> nickname everything, e.g. importing ALEXANDRIA as A, FLEXI-STREAMS as F,
>> BORDEAUX-THREADS as BT or just T, and write our code that way.
>>
>> BR
>> Michał "phoe" Herda
>
> Hi Michał,
>
> Nice to read you here!
>
> From your write to me sounds that the real trouble with :USE is that
> namespace versioning is missing.  Very interesting.

In python or perl, you can control which identifiers to import from a
module into the current namespace.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."