all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 10781@debbugs.gnu.org, "Eric M. Ludlam" <eric@siege-engine.com>
Subject: bug#10781: EIEIO namespace use
Date: Sat, 28 Apr 2012 12:28:41 +0200	[thread overview]
Message-ID: <87aa1wi206.fsf@engster.org> (raw)
In-Reply-To: <jwv8vkafs84.fsf@iro.umontreal.ca> (Stefan Monnier's message of "Fri, 10 Feb 2012 13:39:23 -0500")

Stefan Monnier writes:
> EIEIO needs to be cleaned up so it doesn't intrude all over
> the namespace.
> The worst offenders include:
> - `this'.
> - `slot-*'.
> - `constructor', `destructor'.
> - `delete-instance'.
> - `initialize-instance'.
> - `clone'.
> - `data-debug*'.
> - `make-instance'.
> - `oref'.
> - `oset'.
> - `with-slots'.
> - `object-*'.
> - `class-*'.
> - `next-method-p'.
> - `call-next-method'.
> - error symbols (like no-next-method).
> - ... probably `defmethod', `defclass', and `defgeneric'.

I think this should be a goal for the next merge, but I'm at a loss
regarding how this should be tackled without, you know, breaking
practically every bit of code in CEDET and probably others. Do you have
a suggestion? Maybe even creating EIEIOv2 and slowly porting CEDET to
that?

-David





  reply	other threads:[~2012-04-28 10:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 18:39 bug#10781: EIEIO namespace use Stefan Monnier
2012-04-28 10:28 ` David Engster [this message]
2012-04-28 12:29   ` Eric M. Ludlam
2012-04-28 15:22   ` Stefan Monnier
2012-04-28 15:55     ` David Engster
2012-04-28 19:43       ` Stefan Monnier
2012-04-28 21:03         ` David Engster
2012-04-28 22:29           ` Eric M. Ludlam
2012-04-29  8:06             ` David Engster
2012-04-29 12:14               ` Eric 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=87aa1wi206.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=10781@debbugs.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.