Re: How to cause a compiler warning?

[Alan Mackenzie]

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).