From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
cedet-eieio@lists.sourceforge.net, emacs-devel@gnu.org
Subject: Re: [cedet-eieio] Cleaning up the EIEIO namespace
Date: Wed, 20 Feb 2013 18:41:35 -0500 [thread overview]
Message-ID: <51255F2F.7060707@siege-engine.com> (raw)
In-Reply-To: <87621o84pd.fsf@engster.org>
On 02/19/2013 02:49 PM, David Engster wrote:
> Stefan Monnier writes:
>> For the CL package we solved this problem by leaving the "cl.el" package
>> as a "compatibility package" only required by the packages that haven't
>> been updated to use the new names. CL was so widely used that it will
>> take a *long* time to get rid of all uses of the old names, whereas
>> EIEIO's use is not as pervasive, so we don't necessarily have to do the
>> same for it.
>> This said, maybe it would make sense to move "eieio.el" to "cl-eieio.el"
>> (with clean names, autoloaded from cl-lib) and then make eieio.el
>> into a simple compatibility package full of aliases.
>
> What to do with the other files like eieio-base then? We cannot rename
> it to cl-eieio-base.el because of name clashes, but it also provides
> part of the public, CLOS-like functions.
There is nothing in eieio-base from CLOS. Those are all just handy
base-classes / concepts that I used elsewhere in CEDET.
> To summarize the options so far:
>
> 1) Prefix everything with eieio- and be done with it. Create obsolete
> aliases for the old names and get rid of them "soon" (Emacs
> 25?). Alternatively, create an eieio-compat package with aliases for
> the old names.
>
> 2) Prefix everything with eieio- and create cl- aliases for the
> CLOS-like functionality. Those aliases may be defined in
>
> 2a) the eieio* files itself, or
> 2b) in a separate cl-whatever.el file.
>
> As in 1), define obsolete aliases for the old names or use a compat
> package.
>
> 3) Rename eieio to cl-eieio with clean names (i.e., eieio- and
> cl-prefixes), autoloaded from cl-lib, and make eieio.el a simple
> compatibility package full of aliases.
>
> I'm currently pretty much tied on "2b)+compat package" and 3).
I am fine with most of these ideas, but agree with David that option 3
is pretty good.
Eric
next prev parent reply other threads:[~2013-02-20 23:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 18:10 Cleaning up the EIEIO namespace Stefan Monnier
2013-02-12 22:10 ` David Engster
2013-02-12 23:05 ` Drew Adams
2013-02-13 6:44 ` David Engster
2013-02-13 14:51 ` Drew Adams
2013-02-13 2:47 ` Stefan Monnier
2013-02-13 16:31 ` David Engster
2013-02-14 1:11 ` [cedet-eieio] " Eric M. Ludlam
2013-02-14 13:49 ` Stefan Monnier
2013-02-14 14:00 ` Xue Fuqiao
2013-02-14 21:17 ` David Engster
2013-02-14 22:16 ` Stefan Monnier
2013-02-18 21:32 ` David Engster
2013-02-19 3:26 ` [cedet-eieio] " Stefan Monnier
2013-02-19 19:49 ` David Engster
2013-02-19 21:55 ` Stefan Monnier
2013-02-20 23:41 ` Eric M. Ludlam [this message]
2013-03-29 10:04 ` Vitalie Spinu
2013-03-29 14:20 ` Drew Adams
2013-03-29 21:07 ` Stefan Monnier
2013-02-14 14:30 ` Stefan Monnier
2013-02-14 21:28 ` David Engster
2013-02-14 22:17 ` Stefan Monnier
2013-02-14 22:26 ` David Engster
2013-02-17 17:08 ` Stefan Monnier
2013-02-18 20:55 ` David Engster
2013-02-19 3:15 ` Stefan Monnier
2013-02-13 3:13 ` [cedet-eieio] " Eric M. Ludlam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51255F2F.7060707@siege-engine.com \
--to=eric@siege-engine.com \
--cc=cedet-eieio@lists.sourceforge.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.