unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: cedet-eieio@lists.sourceforge.net, emacs-devel@gnu.org
Subject: Re: [cedet-eieio] Cleaning up the EIEIO namespace
Date: Thu, 14 Feb 2013 08:49:26 -0500	[thread overview]
Message-ID: <jwvr4kjm2w0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <511C39A9.4000403@siege-engine.com> (Eric M. Ludlam's message of "Wed, 13 Feb 2013 20:11:05 -0500")

> setf is part of cl, and couldn't be used at runtime, so I mocked
> up the behavior with something matching aref/aset instead.

Actually, there's a misunderstanding here:
- setf was indeed part of CL, but being a macro it was accepted
  (i.e. you don't need to have it defined at run-time, since it's
  macro-expanded during compilation).
- setf is part of core Elisp in Emacs-24.3.
So maybe we don't need oref/oset at all.

As for Drew's argument, in reality the "cl-" prefix was largely unused
until Emacs-24.3 (it was mostly used to mean "definition internal to
cl.el") where I introduced cl-lib (which does use "cl-" consistently
and replaced the former "cl-" of internal definitions to "cl--").

We could even justify the "cl-" prefix by making cl-lib autoload
`cl-slot-value' from eieio.el.  Or use the "eieio-" prefix everywhere
in eieio*.el and then define "cl-" aliases in cl-lib.el.




        Stefan



  reply	other threads:[~2013-02-14 13:49 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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvr4kjm2w0.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).