From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: sea-level rise of byte-compilation warnings [was: Fixing...byte-compilation warnings...] Date: Sun, 15 Nov 2015 09:38:22 -0800 (PST) Message-ID: References: <5645F670.9040601@online.de> <56460E2B.10603@cs.ucla.edu> <87io54c0es.fsf@web.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1447704544 14032 80.91.229.3 (16 Nov 2015 20:09:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 16 Nov 2015 20:09:04 +0000 (UTC) Cc: Michael Heerdegen , emacs-devel To: daniel sutton Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 16 21:08:52 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZyQ55-0007UR-95 for ged-emacs-devel@m.gmane.org; Mon, 16 Nov 2015 21:08:51 +0100 Original-Received: from localhost ([::1]:48571 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyQ54-0000MU-OR for ged-emacs-devel@m.gmane.org; Mon, 16 Nov 2015 15:08:50 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55151) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zy1G7-0002sG-T1 for emacs-devel@gnu.org; Sun, 15 Nov 2015 12:38:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zy1G2-0008Fy-OK for emacs-devel@gnu.org; Sun, 15 Nov 2015 12:38:35 -0500 Original-Received: from userp1040.oracle.com ([156.151.31.81]:19296) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zy1G2-0008FI-HJ for emacs-devel@gnu.org; Sun, 15 Nov 2015 12:38:30 -0500 Original-Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id tAFHcOx4001802 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 15 Nov 2015 17:38:24 GMT Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id tAFHcNP1019493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 15 Nov 2015 17:38:24 GMT Original-Received: from abhmp0010.oracle.com (abhmp0010.oracle.com [141.146.116.16]) by aserv0121.oracle.com (8.13.8/8.13.8) with ESMTP id tAFHcNfD015296; Sun, 15 Nov 2015 17:38:23 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: userv0021.oracle.com [156.151.31.71] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 156.151.31.81 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:194532 Archived-At: Hi Daniel, I don't disagree with what you say, but your reply belongs in your original topic ("Solving some specific warnings (was: Fixing compilation and byte-compilation warnings before 25.1)"), not in the new one I forked from it. However, it was my bad to introduce this new topic by asking a general question when replying to your statement about this particular message. To my mind it brought up a general problem. My response was not really to what you were trying to say - sorry. I should have just started a new topic, without referring to what you said. And this part of your reply does pertain to the topic I created: > I agree with you that drowning in a sea of worthless > warnings is bad, and that's why I want to fix them. And perhaps this part: > This is a worthless warning precisely because, in a > way, this recursive call outranks the warning. It > ensures non-compliant code still works until the > optional argument is removed. The reason that its > important because its in the core is that this error > is generated when compiling emacs. > > In this case, 3rd parties are given information about > how to not generate warnings: this warning is to only > call display-completions-list with a single argument. > Once this is followed, the warnings cease.