[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fixing compilation and byte-compilation warnings before 25.1

From: Andreas Röhler
Subject: Re: Fixing compilation and byte-compilation warnings before 25.1
Date: Sat, 14 Nov 2015 09:34:11 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100915 Thunderbird/3.1.4

 On 13.11.2015 16:37, Artur Malabarba wrote:
2015-11-13 14:40 GMT+00:00 Andreas Röhler<address@hidden>:
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.
AFAICT the byte-compiler doesn't throw "style warnings". The closest I
can think of that are the "obsolete function/variable" warnings

Don't remember the precise case, here is another one:


Every other warning thrown by the byte-compiler (if memory serves) is
a legitimate "things could go wrong here".

BTW it should be possible to deactivate warnings at a single-symbol base.

For example kept (interactive-p) for a long time and still prefer it, but got the buffer cluttered with warnings, so changed it just for the sake of readability of remaining warnings.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]