[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: moving more cl seq/mapping support into core
From: |
Daniel Colascione |
Subject: |
Re: moving more cl seq/mapping support into core |
Date: |
Fri, 01 Oct 2010 13:36:32 -0700 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 |
On 10/1/2010 4:42 AM, Richard Stallman wrote:
> Every Emacs release adds all sorts of functions that might impinge on
> the user namespace,
>
> Would you please give some examples for a recent release, so it will
> be clear whether you are talking about the same issue?
>
> Most functions in Emacs have name prefixes or suffixes which help
> prevent name conflicts; those names don't pose a problem. We only
> rarely add names like `remove-if' which have nothing in the name to
> keep them out of the user's way, and we normally document such names
> in the manual. If that practice has changed, I would like to know.
Even prefixed functions and symbols can conflict with something the user
has specified; the likelihood is just lower. In general, CL symbols,
even without a namespace qualification, won't cause problems because cl
is *already* so widely-used that anything that would conflict with it
has already been fixed.
Can you provide a real example of something that would break if cl.el
were dumped with Emacs?
Re: moving more cl seq/mapping support into core, MON KEY, 2010/10/02