From: Stefan Monnier <monnier@iro.umontreal.ca>
To: cedet-eieio@lists.sourceforge.net
Cc: "Eric M. Ludlam" <eric@siege-engine.com>, emacs-devel@gnu.org
Subject: Re: Cleaning up the EIEIO namespace
Date: Tue, 12 Feb 2013 21:47:51 -0500 [thread overview]
Message-ID: <jwvpq05rm2h.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87sj51fakd.fsf@engster.org> (David Engster's message of "Tue, 12 Feb 2013 23:10:10 +0100")
>> Here is a patch that attempts to clean up part of the EIEIO namespace.
>> If you like it, please install it upstream, so it will get merged into
>> Emacs later on. If you prefer, I can install it into Emacs directly and
>> you'll merge it later on upstream, of course.
> Thank you for the patch. I know it cannot have been fun. :-)
It was largely mechanical, tho.
> I didn't have time yet to look at your patch in detail. I did apply it
> to CEDET trunk and got byte-compile errors because there's
> eieio-class-parent as well as eieio--class-parent.
Hmm.. there are both eieio-class-parent as well as eieio--class-parent,
but I'm not sure why that would cause a byte-compile error.
> As for the general direction of the cleanup: We did discuss this a bit
> in the bug report you opened for it some time ago, and Eric stated that
> he'd at least like to keep the CLOS-compatible names without having to
> prefix everything with 'eieio-'. Your suggestion was to use the shorter
> 'cl-' prefix instead, and at least I think that is a good compromise. So
> instead of using 'eieio-class-name', for instance, we'd rather use
> 'cl-class-name'. I don't know enough CLOS to see which other names are
> affected by this (but I could easily look it up, of course).
I don't know CLOS either. I also don't know EIEIO enough to know for
sure which functions are "internal" (and can hence move to "eieio-" or
even "eieio--" without any problem) and which are "exported", so that
renaming them has to be done more carefully (with obsolete aliases).
> Regarding the merge procedure: I'm a bit hesitant to merge the current
> CEDET trunk to Emacs just yet because the Java-support is pretty much in
> flux right now, so I'd prefer if you just apply it in Emacs trunk.
OK.
> We were planning to move EIEIO development to Emacs trunk anyway. I'm
> actually hoping that we can remove EIEIO from CEDET upstream some time
> later this year.
Sounds good,
Stefan
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
next prev parent reply other threads:[~2013-02-13 2:47 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 [this message]
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 ` [cedet-eieio] " Eric M. Ludlam
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=jwvpq05rm2h.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cedet-eieio@lists.sourceforge.net \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
/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.