From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: How to cause a compiler warning? Date: Sun, 14 Jan 2024 15:54:09 +0000 Message-ID: <874jffsyfy.fsf@localhost> References: <871qak4n4h.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4520"; mail-complaints-to="usenet@ciao.gmane.io" Cc: =?utf-8?B?Sm/Do28gVMOhdm9yYQ==?= , Richard Stallman , emacs-devel@gnu.org To: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jan 14 16:51:46 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 1rP2m1-0000vt-KE for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Jan 2024 16:51:45 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rP2lU-0003Tm-6g; Sun, 14 Jan 2024 10:51:12 -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 1rP2lR-0003Te-Tj for emacs-devel@gnu.org; Sun, 14 Jan 2024 10:51:09 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rP2lJ-0008AY-GY for emacs-devel@gnu.org; Sun, 14 Jan 2024 10:51:05 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 5EB8B240101 for ; Sun, 14 Jan 2024 16:50:58 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1705247458; bh=NP5RyYhaSuBym11XadSjt+jDsV4k/cgzQS777kvXZAM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=VvzNqh8Rkfunynn4w1jD+t3lcdJ3JzNajW8Yh7Ita9afiy4qDJNaXd7AdAMA3+UOk Puh6AZ4jmZUB3zXTUfWrnhb1PH/0O8mWw1yXTZBh2OzJpggqlE3x0BPx0aTHbDf89t YWkriKEbVy03wu3MhRBlgxaoucFrZmSHbkawnY780/9NfrnmbvfEu//6jGLN9ZWQvE zKXPWITyPJykO5BxNvR6Q0+CZV6HQW+IcRh/5zqtMVQD0OkaUTNpLfk7E+vdu76AQU E16NCXQDP0zwOKiCO1+VVR09RHpiUkjPq9QvbnPpk0Tv2P/SNIy+YvjgWXVEC4+VHa xmTN0DHTmQ7ZQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TCfrK413Lz9rxB; Sun, 14 Jan 2024 16:50:57 +0100 (CET) In-Reply-To: Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable 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:314966 Archived-At: 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'? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at