From: Leo <sdl.web@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Davis Herring <herring@lanl.gov>,
Daniel Colascione <dan.colascione@gmail.com>,
8415@debbugs.gnu.org
Subject: bug#8415: 23.3.50; Extensible Emacs Registers
Date: Tue, 05 Apr 2011 13:42:20 +0800 [thread overview]
Message-ID: <m1bp0l8dab.fsf@th041153.ip.tsinghua.edu.cn> (raw)
In-Reply-To: <jwvei5hbdoq.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 04 Apr 2011 23:07:05 -0400")
On 2011-04-05 11:07 +0800, Stefan Monnier wrote:
> The end point is pretty much the same, but all the intermediate steps
> are safe and easy to check.
I think a structure still is a better approach. It offers uniformity and
allows access to the value stored in each slot so one can easily build a
new register reusing values from an old one which, in some use cases
(defadvice), can be convenient.
>> Well, there's EIEIO. It gives you the ability to easily add methods
>> while not baking the dispatch into each one. On the other hand, it's a
>> quite a bit of code to pull into the core at runtime.
>
> Indeed.
I have thought about using EIEIO in the beginning and ruled it out since
it is required at run time.
Leo
next prev parent reply other threads:[~2011-04-05 5:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 12:29 bug#8415: 23.3.50; Extensible Emacs Registers Leo
2011-04-03 17:21 ` Daniel Colascione
2011-04-04 1:29 ` Leo
2011-04-04 14:29 ` Stefan Monnier
2011-04-04 17:37 ` Leo
2011-04-04 22:19 ` Stefan Monnier
2011-04-04 22:27 ` Daniel Colascione
2011-04-05 1:41 ` Stefan Monnier
2011-04-05 1:49 ` Daniel Colascione
2011-04-05 3:07 ` Stefan Monnier
2011-04-05 5:42 ` Leo [this message]
2011-04-05 13:50 ` Stefan Monnier
2011-04-06 5:00 ` Leo
2011-04-06 15:38 ` Stefan Monnier
2011-04-07 3:13 ` Leo
2011-04-09 1:25 ` Stefan Monnier
2011-06-23 8:11 ` Leo
2011-06-25 13:19 ` Stefan Monnier
2011-06-26 6:42 ` Leo
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=m1bp0l8dab.fsf@th041153.ip.tsinghua.edu.cn \
--to=sdl.web@gmail.com \
--cc=8415@debbugs.gnu.org \
--cc=dan.colascione@gmail.com \
--cc=herring@lanl.gov \
--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 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).