From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: me@wilfred.me.uk, tino.calancha@gmail.com, emacs-devel@gnu.org
Subject: Re: Proposal: make prog2 a macro
Date: Sat, 08 Oct 2016 09:11:09 +0300 [thread overview]
Message-ID: <83d1jbid4y.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-9MgPji9kxS5wvKQe_0maWQas6HdcndLJ_-HFLntxsODQ@mail.gmail.com> (message from Noam Postavsky on Fri, 7 Oct 2016 22:35:04 -0400)
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Fri, 7 Oct 2016 22:35:04 -0400
> Cc: emacs-devel <emacs-devel@gnu.org>, Tino Calancha <tino.calancha@gmail.com>
>
> The "Lisp debugger" may be referring to `debug', not `edebug'. See bug
> #3466 - "have `d' in debugger treat macro expansion like `c' does".
> That said, I think prog2 is rare enough (a quick M-x rgrep over Emacs'
> lisp code found only 66 matches vs 874 for prog1 and 8585 for progn)
> that it wouldn't really matter that much.
Sorry, but I don't find that small number to be negligible. Debugging
Emacs Lisp code in core is already too hard; e.g., too frequently I
need to resort to "printf debugging". I object to any further
difficulties in this area, so if we want to make this a macro, that
bug needs to be fixed first.
In any case, this issue is no more than a nice-to-have, whereas
debugging difficulties are much more important to solve, for a project
which long ago entered the maintenance phase of its life cycle.
Thanks.
next prev parent reply other threads:[~2016-10-08 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 4:16 Proposal: make prog2 a macro Wilfred Hughes
2016-10-07 5:04 ` Tino Calancha
2016-10-07 7:46 ` John Wiegley
2016-10-07 20:34 ` Richard Stallman
2016-10-07 8:08 ` Tino Calancha
2016-10-08 2:12 ` Wilfred Hughes
2016-10-08 2:35 ` Noam Postavsky
2016-10-08 6:11 ` Eli Zaretskii [this message]
2016-10-08 3:40 ` Tino Calancha
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=83d1jbid4y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=me@wilfred.me.uk \
--cc=npostavs@users.sourceforge.net \
--cc=tino.calancha@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.