Re: .: 2 commits - configure.in sw/source

2012-02-15 Thread Michael Stahl
On 15/02/12 19:28, Tor Lillqvist wrote: >> I completely >> fail to see what actual problem could be caused by this. > > And how is that relevant? By the same logic, you could write code that > just "knows" that ints are always 32 bits and whatnot. but no applicable standard requires ints to be 32

Re: .: 2 commits - configure.in sw/source

2012-02-15 Thread Tor Lillqvist
> I completely > fail to see what actual problem could be caused by this. And how is that relevant? By the same logic, you could write code that just "knows" that ints are always 32 bits and whatnot. MSVC mangles struct and class differently (just one char difference, see http://en.wikipedia.org

Re: .: 2 commits - configure.in sw/source

2012-02-15 Thread Stephan Bergmann
On 02/15/2012 05:48 PM, Michael Stahl wrote: WaE: type name first seen using 'class' now seen using 'struct' IMHO this is an utterly pointless warning, because the only difference between "class" and "struct" is the default visibility of the members, and a forward declaration doesn't decla

Re: .: 2 commits - configure.in sw/source

2012-02-15 Thread Michael Stahl
On 13/02/12 09:39, Tor Lillqvist wrote: > commit b7980663f0866629e7c54a085f31dba3d9c26b26 > Author: Tor Lillqvist > Date: Mon Feb 13 09:42:39 2012 +0200 > > WaE: type name first seen using 'class' now seen using 'struct' IMHO this is an utterly pointless warning, because the only differen