From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: How to cause a compiler warning? Date: Sun, 14 Jan 2024 16:26:59 +0000 Message-ID: References: <871qak4n4h.fsf@gmail.com> <874jffsyfy.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21088"; mail-complaints-to="usenet@ciao.gmane.io" Cc: =?iso-8859-1?Q?Jo=E3o_T=E1vora?= , Richard Stallman , emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jan 14 17:27:36 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rP3Kh-0005HI-R2 for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Jan 2024 17:27:35 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rP3KF-0003Z9-KN; Sun, 14 Jan 2024 11:27:07 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rP3KE-0003Z0-Br for emacs-devel@gnu.org; Sun, 14 Jan 2024 11:27:06 -0500 Original-Received: from mail.muc.de ([193.149.48.3]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rP3KB-0007Y3-3i for emacs-devel@gnu.org; Sun, 14 Jan 2024 11:27:06 -0500 Original-Received: (qmail 16972 invoked by uid 3782); 14 Jan 2024 17:27:00 +0100 Original-Received: from acm.muc.de (pd953ae63.dip0.t-ipconnect.de [217.83.174.99]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Sun, 14 Jan 2024 17:27:00 +0100 Original-Received: (qmail 24770 invoked by uid 1000); 14 Jan 2024 16:26:59 -0000 Content-Disposition: inline In-Reply-To: <874jffsyfy.fsf@localhost> X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.3; envelope-from=acm@muc.de; helo=mail.muc.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:314970 Archived-At: Hello, Ihor. On Sun, Jan 14, 2024 at 15:54:09 +0000, Ihor Radchenko wrote: > Alan Mackenzie writes: > >> > 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. > What about `macroexp-warn-and-return'? It is a complicated way of calling byte-compile-warn-x. It probably isn't of interest to Richard at this stage. > -- > Ihor Radchenko // yantar92, > Org mode contributor, > Learn more about Org mode at . > Support Org development at , > or support my work at -- Alan Mackenzie (Nuremberg, Germany).