From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: Fixing compilation and byte-compilation warnings before 25.1 Date: Fri, 13 Nov 2015 07:46:18 -0800 Message-ID: References: <5645F670.9040601@online.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 1447430018 1125 80.91.229.3 (13 Nov 2015 15:53:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Nov 2015 15:53:38 +0000 (UTC) Cc: Juanma Barranquero , emacs-devel@gnu.org To: Andreas =?utf-8?Q?R=C3=B6hler?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 13 16:53:22 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 1ZxGf7-0003Yy-53 for ged-emacs-devel@m.gmane.org; Fri, 13 Nov 2015 16:53:17 +0100 Original-Received: from localhost ([::1]:53735 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxGf6-0005jv-Ht for ged-emacs-devel@m.gmane.org; Fri, 13 Nov 2015 10:53:16 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58070) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxGeZ-0005bO-5N for emacs-devel@gnu.org; Fri, 13 Nov 2015 10:52:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxGeW-0006Gn-Af for emacs-devel@gnu.org; Fri, 13 Nov 2015 10:52:43 -0500 Original-Received: from mail-pa0-x22e.google.com ([2607:f8b0:400e:c03::22e]:35923) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxGeW-0006GZ-5G for emacs-devel@gnu.org; Fri, 13 Nov 2015 10:52:40 -0500 Original-Received: by pacdm15 with SMTP id dm15so103458122pac.3 for ; Fri, 13 Nov 2015 07:52:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:in-reply-to:date:message-id:references :user-agent:mail-followup-to:mime-version:content-type :content-transfer-encoding; bh=arD0OBYeWR4k7JinhS0WwBfnhp9McAi1zbADXOnS2HA=; b=mrrdJSmPMI3nIgmf/cbEC0/RMNMld9dl32Hl0k4iprOaZ4sAAlj960HCXaD5D4c4Uh Q6ZszOvcAyk1eHuj8k2gQsAZGQKhhxlMc3zYcd2GNGcy/vRqkkxNWgCXK6cpdVPCJY9f vWdqXAnHslJ3E++TgGMYj7T0k9u5x5HyWeBbptrpPxv4gBlZrDq1NLw17ApNY2uaIrk2 ThJTtmRF8z5YEXA5fE+vcXRf5FWIMJqQuSMb14zyl0F/wYa/SlAGbxe5CA8oD5IoWRdV bG5sGBeJ7y7+1YUgfxkDX7cLOOlr700buEhmynLN8E9ttJhysMlm+ddmdSM9FwQ5znWn tkAg== X-Received: by 10.68.114.164 with SMTP id jh4mr32473285pbb.129.1447429959535; Fri, 13 Nov 2015 07:52:39 -0800 (PST) Original-Received: from Vulcan.attlocal.net (76-234-68-79.lightspeed.frokca.sbcglobal.net. [76.234.68.79]) by smtp.gmail.com with ESMTPSA id st5sm21222990pab.42.2015.11.13.07.52.36 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 13 Nov 2015 07:52:38 -0800 (PST) Original-Received: by Vulcan.attlocal.net (Postfix, from userid 501) id 470A1105B25AF; Fri, 13 Nov 2015 07:52:36 -0800 (PST) In-Reply-To: <5645F670.9040601@online.de> ("Andreas \=\?utf-8\?Q\?R\=C3\=B6hler\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Fri, 13 Nov 2015 15:40:48 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Mail-Followup-To: Andreas =?utf-8?Q?R=C3=B6hler?= , emacs-devel@gnu.org, Juanma Barranquero X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22e 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:194377 Archived-At: >>>>> Andreas R=C3=B6hler writes: > Suggest as a first step to abolish all pure warnings, keeping errors only. > I.e. tell if something is broken or very probably broken. Abolish all pure > warnings, style warnings etc. Can you clarify what you mean by "abolish"? Is that fixing, or silencing? > Then let's establish a policy for warnings - which needs an api, which > didn't exist or was not right when looked into some years ago. The policy should be: We never have warnings in our build on GNU Linux. Bei= ng warning free on other platforms is also desirable, but more the responsibil= ity of contributors to those platforms. I'm not sure what the "api" is refer you to, though... John