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: Eric Ludlam <ericludlam@gmail.com>, emacs-devel@gnu.org
Subject: Re: Shrinking EIEIO objects
Date: Sat, 03 Jan 2015 10:55:14 +0100	[thread overview]
Message-ID: <87ppawur25.fsf@engster.org> (raw)
In-Reply-To: <jwv4ms88vqv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 02 Jan 2015 21:11:32 -0500")

Stefan Monnier writes:
>> Oh, I missed the call to 'message'...
>
> Sorry, for that: the message call was added for diagnostic purposes,
> it's not meant to be installed.

Phew. :-)

> The "name" arg passed during creation of objects is obsolete, tho.
> But I don't know yet how to tell programmers about it (that's why I
> just added a `message' for now, so that I could tell when the name was
> detected and dropped).

Any chance the byte-compiler might be able to detect this?

>> which made me believe that NAME will stay supported. The name is saved
>> in the hash table `eieio--object-names',
>
> Right, but only when set via eieio-object-set-name-string.

Ah, OK. I think that's a good compromise.

Thanks for working on this! Since Eric also decided to drop support for
Emacs 23.x, I guess we can now really remove EIEIO from CEDET upstream
and just depend on the one that is in Emacs core.

-David



  reply	other threads:[~2015-01-03  9:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 17:59 Shrinking EIEIO objects Stefan Monnier
2015-01-02  2:40 ` Eric Ludlam
2015-01-02 11:22   ` David Engster
2015-01-02 15:04     ` Eric Ludlam
2015-01-02 15:34       ` David Engster
2015-01-03  2:11         ` Stefan Monnier
2015-01-03  9:55           ` David Engster [this message]
2015-01-04 19:34             ` Stefan Monnier
2015-01-09  5:44     ` Eric Abrahamsen
2015-01-09 15:11       ` Stefan Monnier
2015-01-10  2:03         ` Eric Abrahamsen

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=87ppawur25.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=emacs-devel@gnu.org \
    --cc=ericludlam@gmail.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.