On Tue, Dec 22, 2009 at 10:01 PM, Kai Tietz wrote:
> Well, we have here (at least for the native printf functions) to
> assume smallest supported feature-set. By using msvcrt.dll (Vista or
> newer) you are using in fact msvcr80.dll + feature set, which supports
> %ll specifier, but older ms runtim
2009/12/22 Alon Bar-Lev :
> On Tue, Dec 22, 2009 at 7:53 PM, Tor Lillqvist wrote:
>>> But this is *UGLY* And I don't have inttypes.h on all platforms...
>>> For example solaris8 does not define these constants.
>>
>> That is why there exists libraries and higher level languages that
>> make po
On Tue, Dec 22, 2009 at 7:53 PM, Tor Lillqvist wrote:
>> But this is *UGLY* And I don't have inttypes.h on all platforms...
>> For example solaris8 does not define these constants.
>
> That is why there exists libraries and higher level languages that
> make portability easier.
>
> For instanc
> But this is *UGLY* And I don't have inttypes.h on all platforms...
> For example solaris8 does not define these constants.
That is why there exists libraries and higher level languages that
make portability easier.
For instance, GLib has G_GINT64_FORMAT. And then there is Java.
--tml
On Tue, Dec 22, 2009 at 7:44 PM, Tor Lillqvist wrote:
>> I found [1], which states that Microsoft does not support %ll variant.
>> But I checked this in Visual Studio and it is supported.
>> So where is the catch?
>
> There are several different C libraries from Microsoft. Some support
> %ll, some
> I found [1], which states that Microsoft does not support %ll variant.
> But I checked this in Visual Studio and it is supported.
> So where is the catch?
There are several different C libraries from Microsoft. Some support
%ll, some don't. (They all support %I64d.) Use PRId64 etc from
, that's
Hello,
I found [1], which states that Microsoft does not support %ll variant.
But I checked this in Visual Studio and it is supported.
So where is the catch?
Thanks,
Alon.
[1]
http://sourceforge.net/tracker/index.php?func=detail&aid=2818436&group_id=2435&atid=102435
--
