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: Fri, 17 May 2019 13:40:54 +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="19856"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Eli Zaretskii , Stefan Monnier , Emacs developers To: Noam Postavsky Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 17 13:41:56 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 1hRbFL-00051s-Mu for ged-emacs-devel@m.gmane.org; Fri, 17 May 2019 13:41:55 +0200 Original-Received: from localhost ([127.0.0.1]:47067 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRbFK-0008GZ-Bu for ged-emacs-devel@m.gmane.org; Fri, 17 May 2019 07:41:54 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:37843) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hRbEg-0008GU-Ps for emacs-devel@gnu.org; Fri, 17 May 2019 07:41:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hRbEa-0007B9-MG for emacs-devel@gnu.org; Fri, 17 May 2019 07:41:13 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:33588) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hRbET-00075D-2i; Fri, 17 May 2019 07:41:02 -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 1hRbEM-0002Oe-EM; Fri, 17 May 2019 13:40:56 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUNCAVLHBAHAwGQPyFj KRwTCwgLBwPTbiglEgt3NSBd8HceAAACaklEQVQ4jV2TTWvcMBCG1VCbPUbEAe+tLDTnFpkK32Ks kPjmi4KO7rbr0rMDorcKalBvCXZJ/W/zjrTZbPLixd55NB8aaZjxnFeZIlX04zz3kGbGRSvE90av IbbyDgZayX3USPaWJfiEkbtGNrOo9mbN2M4fKVhpeZuynXlrZqQTttPm2IrVr4B+WZwGsGUf9UFx cdp3XQqPA2B7pX2fHnuwA+j6vj94tO0R6HoWgPHHBCnIIwW4tn+V+nP+Arq+i0A+5HzMqX+hhyOa NrbB4wZf/tket3sLUFuFzmc3h+SIk9zuq2KvqkpTdgAvSqkAgA9t7BVL9ucTXwCrXE6DkLm0dlBD jmw4498o1+hJCCELYUGEisd+GkBdSzEUE1ysLedw9hGsAUTRTDDLYSgrkFP0aqXXCCUKVcNFCDwz zy9PkFw/wmCLX3UIVQpRzhXAxVdOwYfCogZ6c7UscwR1IHaQA3185utG3W/Zxc9yngJ4VoHrd7ll mx+2rK18BvQakDyA4dEKeQTs8LAHsc5gLCP+ghzfipLqBbxDwDI24BMln/kZmgQPhWYuahH4Rx7f q9wFIO9ob0XGr0Vxj32856NDDEEFUG8QQJSXKVrSJk5JNEWsiaDzTSPuCaQ7n9UCO18axMIzqYXA O5yM4w1SzmflVExixpj+a+loCWSLtEVdVirO6VVLHjkNblNOgkadJtXxKw0Pf+Ndbhw3Gc94hTVu 9AGMhmECcYPozrrRnBtvzjXrVmnbjUa7FnTUTq+80ZpAEq+xxp1GmJHTtcpGzfp+E4VpiUoSeAJs XqvH1Kz+A2w3b3XR7+DxBPI/QwRvgOyOAAAAAElFTkSuQmCC In-Reply-To: (Noam Postavsky's message of "Fri, 17 May 2019 07:25:01 -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:236650 Archived-At: I had a gander. :-) It doesn't really look that complicated. So we'd introduce a new function with-suppressed-warnings along the lines of with-no-warnings: (byte-defop-compiler-1 with-no-warnings byte-compile-no-warnings) (defun byte-compile-no-warnings (form) (let (byte-compile-warnings) (byte-compile-form (cons 'progn (cdr form))))) And the warnings are issued in contexts like this: (defun byte-compile-warn-obsolete (symbol) "Warn that SYMBOL (a variable or function) is obsolete." (when (byte-compile-warning-enabled-p 'obsolete) ...)) So that would change to (byte-compile-warning-enabled-p 'obsolete symbol) and the main logic for seeing whether we want to warn for that obsolete symbol (etc) would basically be all constrained to the `byte-compile-warning-enabled-p' function? So if we want to go this direction it looks like it can be done in a pretty clean fashion. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no