From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?ISO-8859-1?Q?Andreas_R=F6hler?= Newsgroups: gmane.emacs.devel Subject: Re: Fixing compilation and byte-compilation warnings before 25.1 Date: Fri, 13 Nov 2015 15:40:48 +0100 Message-ID: <5645F670.9040601@online.de> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1447425649 21790 80.91.229.3 (13 Nov 2015 14:40:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 Nov 2015 14:40:49 +0000 (UTC) Cc: John Wiegley , Juanma Barranquero To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 13 15:40:38 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 1ZxFWa-0006nl-Ie for ged-emacs-devel@m.gmane.org; Fri, 13 Nov 2015 15:40:24 +0100 Original-Received: from localhost ([::1]:53394 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxFWZ-0004UG-Ne for ged-emacs-devel@m.gmane.org; Fri, 13 Nov 2015 09:40:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35795) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxFWK-0004Rc-Th for emacs-devel@gnu.org; Fri, 13 Nov 2015 09:40:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZxFWH-0000iy-Nr for emacs-devel@gnu.org; Fri, 13 Nov 2015 09:40:08 -0500 Original-Received: from mout.kundenserver.de ([212.227.17.10]:61127) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZxFWH-0000g4-Fm for emacs-devel@gnu.org; Fri, 13 Nov 2015 09:40:05 -0500 Original-Received: from [192.168.178.31] ([77.12.164.44]) by mrelayeu.kundenserver.de (mreue103) with ESMTPSA (Nemesis) id 0M0bdu-1aGIJC25eQ-00ursL; Fri, 13 Nov 2015 15:40:00 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 In-Reply-To: X-Provags-ID: V03:K0:ZzB4w/rcWAsAf5BJAIgrH/Jydm4uqYJsU2WVVT+119CtjF1mNzO WpUyGcvkLmdfiM9vR0gmxtsxdaDvJS3ykxoSSmiFkuhsLGaC/TZ8jUKTBWph9Lna9Zcjv71 pYWZQYKAZQS51IAKDOKE+FO+T23ecegWfoW8f7ZTcqV76iVAepCbWI3MmMYHbEjEnnM59dw ZhifY8HZFBb/WnOCzZHyg== X-UI-Out-Filterresults: notjunk:1;V01:K0:c+jxJh9jEu4=:5EjBK4XAaqg1rHjGUlxB4r E5yNzyasbifJOZQ3+05dHWmoWFr2qHyC0MYYRsTw1L9aX5n5nXA8pQaHmniqJ5u9PmpN5MpMK kUw7gHXbJmqqtwa81w/sY6n3C//f1Y2LE/vDoqf2/yr8ftqpWyjRQQuLl6G9INMNRP1C5iUtI V6Y9imxrb95nGj1oT6nmlYb5xzGABjORHe/Y7boAmhSokXz60CiLIWKc4xTvgojF8STB/Qnj1 mJE/mgUyqOpAQJcO30BOtJ0rjZzvf9lCxJyWKdhUH1Db9fVBzFwscidPgV8NMsp5Wpoh6YwoC k6IM//ITEaGygqzr3qaQiZb5ljDEvXPlHvxpRVT+TRS44UOcoEdmnpeZ8fpfAXw22w7DwfsJI UH4wCOZzCcuhuWZ1UjyT6Ixg3yOKCh3ws5DrPd8AM1oC8nlZ8TGzxmJ2qicjcCjJrcgtB98U6 2w+WTh+EhB1pIvYMAGligeb3J9VcFgJ39XAqUPMjyAfB2PNb/hCC+FFJSFjwF+qBEv8U1+rwn BODfBEIMydzG/OoU9oS4ZTPpeDkaP4CaOBN6xGsbqZo3VDnRJRvVcttbs94SIejwgPx4gkviX PsAzURzEx12Om8ycHBrhipFIbesJRIvojvwgsp6PLN20UDhoanairsfG6prWgIjLlfH1BxlDl KMWEhCzQnwIieJjBAlp1aoifuB24FwllOoMcdd5QahMl6EuxB5izQ+miXMBruzbZilALXtYx5 ruzFHz/OyfIEigih X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.17.10 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:194366 Archived-At: On 13.11.2015 02:47, John Wiegley wrote: > I'm doing an Emacs build now to test a patch, and it occurs to me how many > warnings and byte-compilation warnings I'm seeing. I'd like us to resolve as > many of these warnings as we can before shipping. It makes the build output > look a bit... unkempt. > > Anyone interested in becoming a champion for this cause? > > John > Hi John, keeping a reasonable warning-management IMO this is another crucial point, because people for now get drowned. 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. 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. Cheers, Andreas