Visual Studio has supported 64-bit int types (long long) since at least Visual Studio 2005. See here: http://msdn.microsoft.com/en-us/library/s3f49ktz(v=vs.80).aspx <http://msdn.microsoft.com/en-us/library/s3f49ktz%28v=vs.80%29.aspx>
_MSC_VER evaluates to the version of the Visual Studio compiler. See here: http://msdn.microsoft.com/en-us/library/b0084kay(v=VS.80).aspx <http://msdn.microsoft.com/en-us/library/b0084kay%28v=VS.80%29.aspx> Eike Rathke wrote: > Hi Regina, > > On Wednesday, 2011-09-07 15:04:47 +0200, Regina Henschel wrote: > >> I see a lot of sal_uInt64 in the code. Is that supported for >> Windows? As far as I know at least the MSVC Express has only 4Byte >> long. > Umm.. now that you mention.. sal/inc/sal/types.h has > > #if (_MSC_VER >= 1000) > typedef __int64 sal_Int64; > typedef unsigned __int64 sal_uInt64; > > so what evaluates _MSC_VER to in MSVCE? > > Also noticing there > > #define SAL_CONST_UINT64(x) x##ui64 > > so the constant I introduced probably should use that. > > If MSVCE doesn't support 64bit values I might do some tricks using the > double mantissa. > > Eike > > > > _______________________________________________ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libreoffice Disclaimer: http://www.peralex.com/disclaimer.html
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice