On 07/22/2013 03:53 PM, bearophile wrote:
> Ali Çehreli:
>
>> Going off topic, why not -w then? If I want to be warned about
>> something, I don't want the program to be compiled anyway but perhaps
>> others want to look at warning messages. :)
>
> There are discussions like this:
> http://d.puremagic.com/issues/show_bug.cgi?id=10147
>
> Bye,
> bearophile
This is what I understand from that discussion:
1) There shouldn't be warnings at all; what we call warnings should be
errors.
I agree with that completely.
2) -w changes the compilation semantics because it may change the result
of __traits(compiles).
I don't understand that at all because anything that affects the
compilation environment can change the behavior of __traits(compiles).
(e.g. the string imports.)
Getting back to -w vs. -wi, I don't understand why to favor -wi over -w.
This is what the documentation says:
-w
enable warnings
-wi
enable informational warnings (i.e. compilation still proceeds
normally)
http://dlang.org/dmd-linux.html
First of all, -w does not only enable warnings, it actually makes them
errors. Great! So, everybody should use -w...
Second, following from that bug report, -wi is useless because it just
gives informational warnings... and then compilation proceeds normally?
It is kind of entertaining I guess but it is completely useless from
program development point of view.
My conclusion: As long as -w exists, keep that on the compilation
command line and ignore -wi.
I would like to hear others' point of view. I am curious how -wi is
preferred over -w by others.
Ali
