From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Towards a cleaner build Date: Sat, 18 May 2019 07:02:28 +0200 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="125940"; 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: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 18 07:02:44 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 1hRrUZ-000WZc-UX for ged-emacs-devel@m.gmane.org; Sat, 18 May 2019 07:02:44 +0200 Original-Received: from localhost ([127.0.0.1]:57705 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRrUY-00018t-LH for ged-emacs-devel@m.gmane.org; Sat, 18 May 2019 01:02:42 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:34033) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRrUS-00018o-RE for emacs-devel@gnu.org; Sat, 18 May 2019 01:02:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hRrUQ-00089q-N1 for emacs-devel@gnu.org; Sat, 18 May 2019 01:02:35 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:46560) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hRrUQ-000891-7r; Sat, 18 May 2019 01:02:34 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=stories) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hRrUK-0004Zz-BU; Sat, 18 May 2019 07:02:30 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAgMAAAAqbBEUAAAADFBMVEUyFCpIKVGPeqMZDBO1 3P+ZAAACdUlEQVQokQ2OX0gTcRzAv6KnFJOrdBMH4UOQziePSkI2zpkaxnKT7TZdi1k6p4OorIxg dg9BT5KGTkGUE9x57sIkoTfB7NyKNVnk5p9l2EsPGcHO2xbInb/2/Pnw4QMhzzA1eujNOFsDbWD2 FCLj3sALjT1IAEnZ9sR0546zw1UEMxTle4C2KtpMN7Qwto5R9PHleJuh/hDcdWT4QAsogaQaaB+p JNTOWCqDixw4GSOTuUSmTrwYB30zN71hZAh/LKmeg0pz6k1CrkIqC+cA9Cwa+jW4GCYxNg7ju1f6 Lw6FIn7WYYb+ZDPSUGzx5OSdtxAiy1LqHysr0yPaJdCOOfjW5dLctN43DAQb5LVc7Gjgka8Rnti8 uHaqTu8rtzdBlriv0Mk6wurFstCBDDVo3z5t7vmTBSquYQ55nhRldQN07p+jeZ5/+hnt6aBXaPf7 eH5UIuVuCMq3qVqeX5ZQdQDelXKn8mS8uWTiNWTuTSXyAYqiJijAz/eo8hrVtLBVAd+VeWeDp5k8 akQy8C68MBd0SLk1NQk8J+OyQ/rSN9IPwHoPpE2roGNdoSIQHSfvjaPJCIM0ETDOHA2tWluia/EP +etFQw6bexxWmUoAUIgRw4v6gudsAQbS9pL+KidihE84DYXZWX3RtXRanEfFYFGGlXUoJgYYnQfo 8txDXIiodq1qDvBkhPa7txnFRtGwgT4pq2Z1wGAJIOiiN6J+8xn7rKk3Dk7XhE6J0eUmEmcgYjGV ITB3kQK6AN1fkYgLPbXpnW9T4P75T8GrEl303/oF+I1ssZbrQvTVXUMr6ORAnNxxH7+0k2chvXkL oa3l1GBA7vgPvYEpmMEEOkEAAAAASUVORK5CYII= In-Reply-To: (Stefan Monnier's message of "Fri, 17 May 2019 12:13:14 -0400") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 80.91.231.51 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:236693 Archived-At: Stefan Monnier writes: > 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? `find-lisp-object-file-name' seems pretty heavy handed... -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no