[Development] Compiler warnings

[Kurt Pattyn]

Christian,

the problem is often when your software has to be integrated into other software and systems, which is almost always the case in life-critical systems.
If your software is controlling a critical component like an X-ray beamer for instance, you’d better be prepared for all kinds of rubbish that can enter your software.
The same holds for cockpit displays for instance; they need to take in a lot of external signals, and that can go wrong.
It is more like ‘Be prepared for the worst and nothing will happen’.

Cheers,

Kurt

> On 17 Oct 2014, at 13:10, Christian Kandeler <christian.kandeler at digia.com> wrote:
> 
> On 10/17/2014 01:06 PM, Milian Wolff wrote:
>> I think you are missing something:
>> 
>> enum Foo {
>> Bar = 1, Baz = 2
>> };
>> 
>> Foo foo = static_cast<Foo>(3);
> 
> If you start to guard against this kind of stuff, where does it end?
> 
> void f(void *p);
> 
> f(reinterpret_cast<void *>(5));
> 
> Is f supposed to catch that?
> 
> 
> Christian
> 
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development