Re: sea-level rise of byte-compilation warnings [was: Fixing...byte-compilation warnings...]

[daniel sutton <danielsutton01@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]

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 <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.  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.
>

[-- Attachment #2: Type: text/html, Size: 2508 bytes --]