While I doubt that - in practice - a compiler would generate incorrect code in
this case, I agree that it's a possibility unless we compile with
"-fno-strict-aliasing". But I don't want to do that, because it could make the
whole of the code less efficient. (And changing the Makefiles to compi
Regarding casting between dissimilar types:
> c++ -c -Iinclude -I../UsageEnvironment/include -I../groupsock/include -I.
> -O2 -DSOCKLEN_T=socklen_t -D_LARGEFILE_SOURCE=1 -D_FILE_OFFSET_BITS=64
> -Wall -DBSD=1 MatroskaFileParser.cpp
> MatroskaFileParser.cpp: In member function Boolean
> MatroskaFi
>> complains about the following statement:
>>
>> result = *(float*)&resultAsUnsigned;
No, this compiler warning message does not indicate a bug in the code.
"resultAsUnsigned" is a 4-byte value that stores a 'float'; it is not an
unsigned value that gets converted to a float.
>> This li
> Hi.
>
> I downloaded live.2012.08.29.tar.gz a few minutes ago, and built in on my
> linux box*.
>
> I saw several warnings issued by the compiler.
>
> I've been looking closely at each, and I think there's an actual problem
> with one of them.
>
> c++ -c -Iinclude -I../UsageEnvironment/inclu
