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: other output Date: Mon, 17 Jun 2019 18:40:24 -0400 Message-ID: References: <83zhn6zkgf.fsf@gnu.org> <83a7eo9nsh.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="162549"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 18 00:42:02 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.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hd0K6-000g86-Iy for ged-emacs-devel@m.gmane.org; Tue, 18 Jun 2019 00:41:58 +0200 Original-Received: from localhost ([::1]:52356 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hd0K5-0007BB-JF for ged-emacs-devel@m.gmane.org; Mon, 17 Jun 2019 18:41:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36689) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hd0Iy-0006Js-BN for emacs-devel@gnu.org; Mon, 17 Jun 2019 18:40:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hd0Ix-0006Cc-An for emacs-devel@gnu.org; Mon, 17 Jun 2019 18:40:48 -0400 Original-Received: from [195.159.176.226] (port=59072 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hd0Iv-0005wb-7A for emacs-devel@gnu.org; Mon, 17 Jun 2019 18:40:47 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hd0Ih-000ecJ-Bf for emacs-devel@gnu.org; Tue, 18 Jun 2019 00:40:31 +0200 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:8MAFtpmMEze8zM1rvwfpGZ8gohI= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:237808 Archived-At: > eieio.el: ‘object-print’ is an obsolete generic function (as of 26.1); use > ‘cl-print-object’ instead. > > These are output by cl-defmethod/cl-defgeneric, and we're defining an > (obsolete) fallback method, so we should suppress this warning. Do we > need a new mechanism or do we have something to cover this? Presumably wrapping those `cl-defmethod`s in a with-suppressed-warnings should do the trick. > *Warning* default value of <> tokens changed to QUERY, was NULL_TOKEN > *Warning* default value of <> tokens changed to TRUE, was QUERY > *Warning* default value of <> tokens changed to FALSE, was TRUE > Grammar in javascript.el contains 2 useless nonterminals and 4 useless rules > Grammar in js-wy.el contains 2 useless nonterminals and 4 useless rules > Grammar in python-wy.el contains 2 useless nonterminals and 3 useless rules > Grammar in python-wy.el contains 4 shift/reduce conflicts > Grammar in python.el contains 2 useless nonterminals and 3 useless rules > Grammar in python.el contains 4 shift/reduce conflicts > > These are from cedet, and are warning about grammars containing... > useless rules? Perhaps this is more useful at run-time than at compile > time? This is like running `yacc`: you want those warnings when you run `yacc`, not when you use the resulting grammar. > Loading /home/larsi/src/emacs/trunk/lisp/international/uni-name.el (source)... > > Hm... a "Loading" in the middle here? Does anybody know why? I guess something's using `load` instead of `require`? > latin-ltx: 1535 rules (+ 0 conflicts)! > Uhm... That doesn't seem very useful to me -- only output that if there > are any conflicts? Agreed (and I plead guilty), Stefan