all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org, cedet-eieio@lists.sourceforge.net,
	'Stefan Monnier' <monnier@iro.umontreal.ca>,
	"'Eric M. Ludlam'" <eric@siege-engine.com>
Subject: Re: Cleaning up the EIEIO namespace
Date: Wed, 13 Feb 2013 07:44:32 +0100	[thread overview]
Message-ID: <87obfog1bj.fsf@engster.org> (raw)
In-Reply-To: <95379C8C6AEF4A02A79D2958B6864FB0@us.oracle.com> (Drew Adams's message of "Tue, 12 Feb 2013 15:05:51 -0800")

Drew Adams writes:
>> 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'.
>
> So does this mean that we can no longer know from the `cl-' prefix which library
> is involved?
>
> (I don't mean which file in the library, but which library.  In the past, `cl-'
> pretty much indicated library `cl' - either file cl.el or one of its related
> files cl-mac.el, cl-seq.el etc.)

That is certainly a valid concern. But I (and I guess Stefan, too) was
thinking more along the lines that 'cl' essentially means "common lisp",
and EIEIO being a CLOS implementation, this would make sense. Maybe it
would be cleaner to also rename the eieio- files to cl-clos-, but that
would break a lot of things out there.

-David



  reply	other threads:[~2013-02-13  6:44 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 [this message]
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                     ` [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=87obfog1bj.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=cedet-eieio@lists.sourceforge.net \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=eric@siege-engine.com \
    --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.