From: Alan Mackenzie <acm@muc.de>
To: "João Távora" <joaotavora@gmail.com>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: How to cause a compiler warning?
Date: Sun, 14 Jan 2024 16:21:43 +0000 [thread overview]
Message-ID: <ZaQKF46qVTm8P6uR@ACM> (raw)
In-Reply-To: <CALDnm50BcZA+iSX2G=DF8xTAtjPYFzDQeAFEOanjk319pDJZ1g@mail.gmail.com>
Hello, João.
On Sun, Jan 14, 2024 at 15:43:51 +0000, João Távora wrote:
> On Sun, Jan 14, 2024, 13:01 Alan Mackenzie <[1]acm@muc.de> wrote:
> > > I would like to make the cond* macro generate warnings in
> certain
> > > cases, when it is being copiled. What is the recommended way
> to do
> > > that?
> > Probably call byte-compile-warn at macro-expansion time?
> Most assuredly not. This may give an incorrect file position for
> the
> warning.
> Aight, I wasnt thaaat far off the mark..
> Since 29.1, the correct function for a warning has been
> byte-compile-warn-x.
> Self-evidently so, of course, the 'x' standing for "correct".
Something like that, yes.
> Anyway, what about <29 compatible code?
What about it? Richard isn't working on < 29 code at the moment.
> João
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2024-01-14 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 3:09 How to cause a compiler warning? Richard Stallman
2024-01-14 3:20 ` João Távora
2024-01-14 13:01 ` Alan Mackenzie
2024-01-14 15:43 ` João Távora
2024-01-14 16:21 ` Alan Mackenzie [this message]
2024-01-15 0:16 ` João Távora
2024-01-17 12:25 ` Alan Mackenzie
2024-01-17 13:40 ` João Távora
2024-01-18 12:05 ` Alan Mackenzie
2024-01-18 12:26 ` João Távora
2024-01-14 15:54 ` Ihor Radchenko
2024-01-14 16:26 ` Alan Mackenzie
2024-01-17 3:29 ` Richard Stallman
2024-01-17 11:59 ` Alan Mackenzie
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=ZaQKF46qVTm8P6uR@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--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).