Re: [Mingw-w64-public] conflicting types?

2012-10-19 Thread Roger Pack
>> Who is defining const as an empty macro? That doesn't seem right. > > > C++ only makes it undefined behavior, and the rules are fuzzy at best (seems > that it's only undefined behavior when the translation unit includes a > standard header): > http://stackoverflow.com/questions/2726204/c-preproc

Re: [Mingw-w64-public] conflicting types?

2012-10-19 Thread Ruben Van Boxem
2012/10/19 Ozkan Sezer > On Fri, Oct 19, 2012 at 2:00 AM, Roger Pack wrote: > >> Something is messing with the defines in your code, it works fine when I > >> tested. > >> > >> $ x86_64-w64-mingw32-gcc -E > >> mingw-w64/trunk/mingw-w64-headers/crt/intrin.h | grep wcslen > >> size_t __attribu

Re: [Mingw-w64-public] conflicting types?

2012-10-19 Thread Ozkan Sezer
On Fri, Oct 19, 2012 at 2:00 AM, Roger Pack wrote: >> Something is messing with the defines in your code, it works fine when I >> tested. >> >> $ x86_64-w64-mingw32-gcc -E >> mingw-w64/trunk/mingw-w64-headers/crt/intrin.h | grep wcslen >> size_t __attribute__((__cdecl__)) wcslen(const wchar_t