unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Stephen Gildea <stepheng+emacs@gildea.com>
Cc: emacs-devel@gnu.org
Subject: Re: (declare (debug 0))
Date: Wed, 20 Oct 2021 08:33:34 -0400	[thread overview]
Message-ID: <jwvsfwvq3kx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <54799.1634707328@pental> (Stephen Gildea's message of "Tue, 19 Oct 2021 22:22:08 -0700")

Stephen Gildea [2021-10-19 22:22:08] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>>   I must say I [had] no idea that 0 was supposed to be treated specially.
>>   
>>   I would have written (&rest sexp) instead, tho more likely I would have
>>   written nothing at all and relies on the default behavior of Edebug....
>
> If even you didn't know about (debug 0), it sounds like I should update
> the manual to recommend (debug nil) instead.
>
> I do like the idea of offering (continuing to offer) a simple shorthand
> that says "do not instrument args", even though that is the default and
> is rarely used in current code.  Adding an explicit declaration saves
> later readers/maintainers of a macro definition from having to figure
> out whether a "debug" declaration is missing.

In my experience, macros whose args should not be instrumented are not
the most common, by far, and (&rest sexp) is sufficiently short and
clear for them.  I don't see any need to have something shorter.


        Stefan




  reply	other threads:[~2021-10-20 12:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  1:40 (declare (debug 0)) Stephen Gildea
2021-10-19 12:29 ` Stefan Monnier
2021-10-20  5:22   ` Stephen Gildea
2021-10-20 12:33     ` Stefan Monnier [this message]
2021-10-21  1:46       ` Stephen Gildea
2021-10-21 16:44         ` Stefan Monnier
2021-10-21 17:10           ` Eli Zaretskii
2021-10-21 19:04             ` Stephen Gildea
2021-10-21 19:17               ` Eli Zaretskii

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=jwvsfwvq3kx.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=stepheng+emacs@gildea.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).