From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Colascione <dan.colascione@gmail.com>
Cc: Davis Herring <herring@lanl.gov>,
8415@debbugs.gnu.org, Leo <sdl.web@gmail.com>
Subject: bug#8415: 23.3.50; Extensible Emacs Registers
Date: Mon, 04 Apr 2011 23:07:05 -0400 [thread overview]
Message-ID: <jwvei5hbdoq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4D9A7537.5030005@gmail.com> (Daniel Colascione's message of "Mon, 04 Apr 2011 18:49:43 -0700")
>> It's the difference between "one simple obviously correct change" and
>> "one big change that might be correct".
> I see your point, though both approaches would be pretty small changes
> in the scheme of things. If you want to split the change into smaller
> steps, that's fine so long as we eventually aim to get rid of the
> typecase polymorphism.
The end point is pretty much the same, but all the intermediate steps
are safe and easy to check.
> 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.
Stefan
next prev parent reply other threads:[~2011-04-05 3:07 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 [this message]
2011-04-05 5:42 ` Leo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvei5hbdoq.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=8415@debbugs.gnu.org \
--cc=dan.colascione@gmail.com \
--cc=herring@lanl.gov \
--cc=sdl.web@gmail.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 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.