[Issue 14367] Print warnings by default

Mar 28, 2015

bearophile_hugs@eml.cc

Mar 29, 2015

Kenji Hara

Apr 11, 2015

yebblies

Apr 11, 2015

Martin Krejcirik

Apr 11, 2015

bearophile_hugs@eml.cc

Dec 08, 2015

Don

Dec 08, 2015

Sobirari Muhomori

Dec 09, 2015

bearophile_hugs@eml.cc

Dec 17, 2022

Iain Buclaw

Dec 13

dlangBugzillaToGithub

https://issues.dlang.org/show_bug.cgi?id=14367 bearophile_hugs@eml.cc changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bearophile_hugs@eml.cc --- Comment #1 from bearophile_hugs@eml.cc --- See also Issue 13040 , Issue 10147 --

https://issues.dlang.org/show_bug.cgi?id=14367 Martin Krejcirik <mk@krej.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mk@krej.cz --- Comment #3 from Martin Krejcirik <mk@krej.cz> --- (In reply to Shammah Chancellor from comment #0) > DMD currently does not print warning by default. This should be changed so that people are notified of deprecated features during compilation and can start fixing them. It will come as a surprise when these features are The whole point of deprecation messages (-dw) is to notify people of pending deprecation. Warnings (-wi) are something completely different. They warn about something which may or may not be wrong (buggy). Sometimes warnings are used as a first stage before deprecation, but IMHO these two should not be mixed. Since -dw is turned on by default, there is no need for -wi by default too. --

https://issues.dlang.org/show_bug.cgi?id=14367 --- Comment #4 from bearophile_hugs@eml.cc --- (In reply to Martin Krejcirik from comment #3) > Since -dw is turned on by default, there is no need for -wi by default too. I'd like warnings by default, regardless what the compiler does regarding deprecated features. --

December 08, 2015

[Issue 14367] Print warnings by default

Posted by Don

Permalink

Don

Permalink

https://issues.dlang.org/show_bug.cgi?id=14367

--- Comment #5 from Don <clugdbug@yahoo.com.au> ---
I think this bug should be closed as invalid. As stated in comment 3, warnings and deprecations are two very different things. The bug report is based on the misconception that they are the same.

deprecation = this code used to be correct, but now it is an error. The code
must be fixed, but it is not urgent.
warning = the code might be perfectly correct.

Bearophile's comment 4 is something different. It is a real issue. I think it would best be fixed by removing warnings from the compiler entirely (which is in practice what Bearophile is asking for, if they are enabled by default they are just errors). The whole idea of an "optional error" is absurd. If a single library does not compile without warnings, then the app cannot be compiled with warnings enabled either. So warnings are usable only if all libraries respect them, which means they are not optional for libraries! But that is a discussion for a different place.

--

https://issues.dlang.org/show_bug.cgi?id=14367 --- Comment #6 from Sobirari Muhomori <dfj1esp02@sneakemail.com> --- Warnings can work as out of line code style checkers. Breaking compilation on enabled warnings doesn't work well for this. --

https://issues.dlang.org/show_bug.cgi?id=14367 --- Comment #7 from bearophile_hugs@eml.cc --- (In reply to Don from comment #5) > Bearophile's comment 4 is something different. It is a real issue. I think it would best be fixed by removing warnings from the compiler entirely (which is in practice what Bearophile is asking for, if they are enabled by default they are just errors). Nope. Warnings active on default should not stop compilation. So they are still different from errors. (Note that other good languages acts like I have suggested D to act). What I am asking is an obvious improvement for the D compiler. --

https://issues.dlang.org/show_bug.cgi?id=14367 Iain Buclaw <ibuclaw@gdcproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P4 --

https://issues.dlang.org/show_bug.cgi?id=14367 --- Comment #8 from dlangBugzillaToGithub <robert.schadek@posteo.de> --- THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/dmd/issues/18965 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB --

Forums