From: "Richard M. Stallman" <rms@gnu.org>
To: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: emacs-devel@gnu.org
Subject: Re: Enhancement suggestion: prin1 extension mechanism
Date: Fri, 12 Sep 2008 20:30:03 -0400 [thread overview]
Message-ID: <E1KeJ1X-0004WC-LK@fencepost.gnu.org> (raw)
In-Reply-To: <200809110325.m8B3PYFE031034@projectile.siege-engine.com> (eric@siege-engine.com)
I have two questions:
* Why have cedet-edebug-prin1-to-string
construct a function definition rather than
scan the list cedet-edebug-prin1-extensions directly?
* Would it make sense to define the conditions in a more structured
(and thus, less general and more predictable) way?
For instance, could it fit naturally into the way EIEIO defines a class?
next prev parent reply other threads:[~2008-09-13 0:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 3:25 Enhancement suggestion: prin1 extension mechanism Eric M. Ludlam
2008-09-13 0:30 ` Richard M. Stallman [this message]
2008-09-14 15:47 ` Re[2]: " Eric M. Ludlam
2008-09-15 13:23 ` Richard M. Stallman
2008-09-15 16:31 ` Ted Zlatanov
2008-09-13 2:22 ` Stefan Monnier
2008-09-13 11:13 ` Helmut Eller
2008-09-13 19:22 ` Stefan Monnier
2008-09-13 21:13 ` Helmut Eller
2008-09-14 19:35 ` Stefan Monnier
2008-09-14 22:09 ` Helmut Eller
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=E1KeJ1X-0004WC-LK@fencepost.gnu.org \
--to=rms@gnu.org \
--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).