From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Towards a cleaner build Date: Sat, 18 May 2019 08:43:55 -0400 Message-ID: References: <831s0xd3z1.fsf@gnu.org> <83pnohbhny.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="79509"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Eli Zaretskii , Noam Postavsky , Emacs developers To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 18 14:56:38 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hRyt9-000KW2-UB for ged-emacs-devel@m.gmane.org; Sat, 18 May 2019 14:56:36 +0200 Original-Received: from localhost ([127.0.0.1]:33753 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRyt9-0006lo-0I for ged-emacs-devel@m.gmane.org; Sat, 18 May 2019 08:56:35 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:40460) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRysw-0006Wm-C4 for emacs-devel@gnu.org; Sat, 18 May 2019 08:56:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hRyhA-0004tb-Iy for emacs-devel@gnu.org; Sat, 18 May 2019 08:44:13 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:30934) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hRyh6-0004pY-01; Sat, 18 May 2019 08:44:08 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 67EC944268D; Sat, 18 May 2019 08:44:03 -0400 (EDT) Original-Received: from mail02.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 3EEC444265F; Sat, 18 May 2019 08:44:02 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1558183442; bh=EE486k5U2qCpSx1SkXsGBDfyvVsTg40oB9hudxje5Y0=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=G+WIiV39c4PLoj1RoqTJlyp/R/hlRVtFqJHQd7TOF0t5TvIlFT8Jkr8BUDHCFeK1O +T0dDTkuWr+oLPgqbdQFRRqMIdT0uOXl4USg5cML/rdboG5h9h4MlCXjt1hiE1bLkr MAoVG9OG2D1uI11/KSEqjX0YrcFviX18eU533+T7rZr4Tte36u74P6/XJmESIY2kaQ sYfsV3XyphIlaiGq0c6xUkcSy47IYMNKEg5KVCPKOhb7gvHmC8YawgWxbowWGaKtvJ 0ybpuZNuC+4j9cKqA8OVbFVwW9vavvPaYnjRSt1b6jHuoECTafXdxmnTbwWybcOS80 DmOWRXtSeH6oA== Original-Received: from ceviche (184-175-13-248.dsl.teksavvy.com [184.175.13.248]) by mail02.iro.umontreal.ca (Postfix) with ESMTPSA id 05EDD1207A2; Sat, 18 May 2019 08:44:01 -0400 (EDT) In-Reply-To: (Lars Ingebrigtsen's message of "Sat, 18 May 2019 07:02:28 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:236714 Archived-At: >> Note that if a function/variable FOO is defined as obsolete in file BAR, then >> I think we'd ideally want to silence all warnings for uses of FOO made >> within BAR. > Determining the current file is easy enough (with > `byte-compile-current-file'), but what's the best way to determine what > file that obsolete function came from? I'm not suggesting we encode the above condition in the code. As I said elsewhere, I think trying to be too clever in which warnings to automatically silence quickly gets to diminishing returns. More important is the support for the author to be able to silence those warnings which are false positives since that works regardless if we could come up with a way to detect it automatically or not. Stefan