Roman Ivanov:

> This probably has been discussed to death before,

Don't worry, it was not discussed enough. Discussions that go nowhere aren't 
enough.


> but what are the big issues with checking for overflows

There are no big issues for checking for overflows. Even C# has them and they 
work. A syntax is needed to disable them locally, but this is not hard to 
invent. Plus probably two compilation switches to disable/enable them locally. 
People that don't want them just disable them. (My theory is that the slowdown 
caused by them is small enough that lot of people will want to keep them 
enabled in release mode too). Fixing Phobos to make it overflow-checking 
compliant will require some work, so it's better to introduce them sooner than 
later. Some other technical difficulties may remain, but in the end it's mostly 
a matter of finding someone willing to implement this feature and it's a matter 
of what Walter will accept.


> and prohibiting (or giving warnings) on implicit unsigned-to-signed 
> conversion?

This warning is useful, I use it on default when I write C code. Walter doesn't 
like warning in general (because he says warnings become de facto errors), and 
because he says this warning creates too many false positives.

Regarding warnings, I am waiting for some DMD warnings to become errors, like:
http://d.puremagic.com/issues/show_bug.cgi?id=4216
http://d.puremagic.com/issues/show_bug.cgi?id=3836
Plus there are other warnings I'd like to have, like the "unused variable" one.

Bye,
bearophile

Reply via email to