From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 11935@debbugs.gnu.org, rms@gnu.org
Subject: bug#11935: XINT etc. should be functions
Date: Mon, 16 Jul 2012 19:12:14 +0300 [thread overview]
Message-ID: <83629nbs81.fsf@gnu.org> (raw)
In-Reply-To: <50042B0F.9050105@cs.ucla.edu>
> Date: Mon, 16 Jul 2012 07:54:07 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> Cc: 11935@debbugs.gnu.org, rms@gnu.org
>
> There are important advantages to not inlining: you can put
> breakpoints on them, for example.
Why would we need to put a breakpoint on a function that replaces the
XINT macro? We've lived with a macro (where you cannot put a
breakpoint) for many years without any problems (AFAIK). We have
debugger commands to display values of Lisp integers. So I don't
think debuggability will be a problem in this particular case
(although it might be in others).
next prev parent reply other threads:[~2012-07-16 16:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 15:07 bug#11935: XINT etc. should be functions Paul Eggert
2012-07-14 2:20 ` bug#11935: [TRUNCATED MESSAGE 2746 87596] " Richard Stallman
2012-07-15 13:41 ` Paul Eggert
2012-07-15 22:06 ` Stefan Monnier
2012-07-16 14:54 ` Paul Eggert
2012-07-16 16:12 ` Eli Zaretskii [this message]
2012-07-16 21:40 ` Paul Eggert
2012-07-16 18:19 ` Richard Stallman
2012-07-16 22:46 ` Paul Eggert
2012-07-17 3:04 ` Eli Zaretskii
2012-07-17 3:54 ` Paul Eggert
2012-07-24 2:20 ` Paul Eggert
2012-07-24 9:07 ` Stefan Monnier
2012-07-24 13:45 ` Paul Eggert
2012-07-24 21:57 ` Stefan Monnier
2012-07-25 4:07 ` Paul Eggert
2012-07-15 14:41 ` Chong Yidong
2012-07-15 16:40 ` Paul Eggert
2012-07-16 2:22 ` Chong Yidong
2012-07-16 14:54 ` Paul Eggert
2013-06-06 15:56 ` Paul Eggert
2013-06-06 16:36 ` Andreas Schwab
2013-06-13 16:30 ` Paul Eggert
2013-06-06 16:42 ` Stefan Monnier
2013-06-09 0:52 ` Paul Eggert
2013-06-09 3:04 ` Stefan Monnier
2013-06-09 4:37 ` James Cloos
2013-06-09 6:59 ` Jan Djärv
2013-06-09 7:13 ` Paul Eggert
2013-06-09 15:57 ` Stefan Monnier
2013-06-13 14:45 ` Paul Eggert
2013-06-13 20:08 ` Stefan Monnier
2013-06-15 6:43 ` Paul Eggert
2013-06-15 14:22 ` Stefan Monnier
2013-06-17 6:05 ` Paul Eggert
2013-06-09 6:56 ` Jan Djärv
2013-06-09 7:23 ` Paul Eggert
2013-06-09 9:18 ` Jan Djärv
2013-06-09 14:25 ` Juanma Barranquero
2013-06-09 16:05 ` Jan Djärv
2013-06-10 13:40 ` Barry OReilly
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=83629nbs81.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11935@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=rms@gnu.org \
/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).