From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: daniel sutton Newsgroups: gmane.emacs.devel Subject: Re: sea-level rise of byte-compilation warnings [was: Fixing...byte-compilation warnings...] Date: Sun, 15 Nov 2015 11:47:19 -0600 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: multipart/alternative; boundary=001a113f8f3c58ea1b052497e2ed X-Trace: ger.gmane.org 1447704598 14820 80.91.229.3 (16 Nov 2015 20:09:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 16 Nov 2015 20:09:58 +0000 (UTC) Cc: Michael Heerdegen , emacs-devel To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 16 21:09:57 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 1ZyQ68-0000st-Mg for ged-emacs-devel@m.gmane.org; Mon, 16 Nov 2015 21:09:56 +0100 Original-Received: from localhost ([::1]:48580 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZyQ68-0002DL-6h for ged-emacs-devel@m.gmane.org; Mon, 16 Nov 2015 15:09:56 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56234) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zy1Ob-00046p-OY for emacs-devel@gnu.org; Sun, 15 Nov 2015 12:47:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zy1Oa-0001WR-Bs for emacs-devel@gnu.org; Sun, 15 Nov 2015 12:47:21 -0500 Original-Received: from mail-io0-x22a.google.com ([2607:f8b0:4001:c06::22a]:34402) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zy1Oa-0001WJ-5P for emacs-devel@gnu.org; Sun, 15 Nov 2015 12:47:20 -0500 Original-Received: by ioir85 with SMTP id r85so99443912ioi.1 for ; Sun, 15 Nov 2015 09:47:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pHM/qWcc83TLBudxln00E4fiXY0pISEIeGeKVkndjew=; b=HlBHFv+s41qTqieNN7LLPY4drnhGR6kxPULkSQCwLbCHk/RpvR532kdAqJk5tiZ4Q1 k2eZY++jgLQiL2p3ySSY87mFNcH4h4cQNmpeaQKc2N8VfT9eD6EGFyJkaSi9Nhw/gabz b73WISb9wa1E87230bWu3GIGqchhEOp5jPJt3bHL6x50Nb39dQKm5dTPwNTnKzCCCIKY RoYH1otHN2aw6vUlUXhu7cYb7G+H+cP0WFTpVt/P/WVA6XiBBmVSzbd3KIMX6aHv4y70 5LoVJYn55vSyBqB6IresqafuJHXi0wNimWeCsMFbVVzyPnL6zg/MnHDWhKbS2QsEj5jj aS5Q== X-Received: by 10.107.8.69 with SMTP id 66mr32822165ioi.34.1447609639691; Sun, 15 Nov 2015 09:47:19 -0800 (PST) Original-Received: by 10.107.15.229 with HTTP; Sun, 15 Nov 2015 09:47:19 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4001:c06::22a 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:194534 Archived-At: --001a113f8f3c58ea1b052497e2ed Content-Type: text/plain; charset=UTF-8 Oh i apologize. I'm still quite new to all of this and I don't have a firm understanding of what third party creators go through. Do you have some code in mind that I could byte compile to see these warnings so I can get a sense of what issues there are? Granted I see lots of warnings when grabbing from Melpa but I always dismiss the buffer. So maybe we could use one clear example to have tangible issues and a canonical example of annoyances that third party creators go through. On Sun, Nov 15, 2015 at 11:38 AM, Drew Adams wrote: > 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. > --001a113f8f3c58ea1b052497e2ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Oh i apologize.

I'm still quite new= to all of this and I don't have a firm understanding of what third par= ty creators go through. Do you have some code in mind that I could byte com= pile to see these warnings so I can get a sense of what issues there are? G= ranted I see lots of warnings when grabbing from Melpa but I always dismiss= the buffer. So maybe we could use one clear example to have tangible issue= s and a canonical example of annoyances that third party creators go throug= h.=C2=A0



On Sun, Nov 15, 2015 at 11:38 AM, Drew Ada= ms <drew.adams@oracle.com> wrote:
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.=C2=A0 To my mind it brought up a
general problem.=C2=A0 My response was not really to what you
were trying to say - sorry.=C2=A0 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.=C2=A0 It
> ensures non-compliant code still works until the
> optional argument is removed.=C2=A0 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.

--001a113f8f3c58ea1b052497e2ed--