On Fri, Mar 5, 2010 at 12:20 AM, Jim Michaels wrote:
> in MSVC,
> __int64 x=12345678901234567i64;
>
> point 1: this type __int64 doesn't require me to #include to
> define it. in mingw and mingw-w64, one must #include . why?
It is enough, I guess.. Include windows.h if you want,
why is that a p
in MSVC,
__int64 x=12345678901234567i64;
point 1: this type __int64 doesn't require me to #include to define
it. in mingw and mingw-w64, one must #include . why?
point 2: there are also __int32 __int16 and __int8 types.
point 3: mingw does not utilize the i64 constant thingy (whatever it's
2010/3/4 Tor Lillqvist :
>> Maybe, but exception handling still won't work.
>
> Isn't there other things also that are incompatible, like vtables and
> whatnot? Doesn't some FAQ say that different C++ compilers use
> different name mangling on purpose because even if they would use the
> same mangl
> Maybe, but exception handling still won't work.
Isn't there other things also that are incompatible, like vtables and
whatnot? Doesn't some FAQ say that different C++ compilers use
different name mangling on purpose because even if they would use the
same mangling, one could still not in general
