Re: How to cause a compiler warning?

[Alan Mackenzie]

Hello, João.

On Sun, Jan 14, 2024 at 03:20:14 +0000, João Távora wrote:
> Richard Stallman <rms@gnu.org> writes:

> > [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> > [[[ whether defending the US Constitution against all enemies,     ]]]
> > [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> >
> > 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.

Since 29.1, the correct function for a warning has been
byte-compile-warn-x.

-- 
Alan Mackenzie (Nuremberg, Germany).