Klaus Schmidinger wrote:
> On 02/19/08 21:26, Ludwig Nussel wrote:
> > Klaus Schmidinger wrote:
> >> Apparently there are macros for this, like PRId64 and such.
> >> But i don't like having to write something like
> >>
> >> int64_t n = ...;
> >> printf("Some number %" PRId64 "\n", n);
> >>
> >>
On 02/20/08 05:37, Theunis Potgieter wrote:
> I am no expert, but if they teach STL for C++ why not use that instead
> which is suppose to be type cast safe, instead of the older printf
> mechanism. I don't want to start a war on what the best method is. But
> just wanted to understand. Or would th
I am no expert, but if they teach STL for C++ why not use that instead which
is suppose to be type cast safe, instead of the older printf mechanism. I
don't want to start a war on what the best method is. But just wanted to
understand. Or would the cost in time be too high to convert everything?
m
On 02/19/08 21:26, Ludwig Nussel wrote:
> Klaus Schmidinger wrote:
>> Apparently there are macros for this, like PRId64 and such.
>> But i don't like having to write something like
>>
>> int64_t n = ...;
>> printf("Some number %" PRId64 "\n", n);
>>
>> Don't know if the gettext mechanisms would
Klaus Schmidinger wrote:
> Apparently there are macros for this, like PRId64 and such.
> But i don't like having to write something like
>
> int64_t n = ...;
> printf("Some number %" PRId64 "\n", n);
>
> Don't know if the gettext mechanisms would be able to handle
>
>tr("Some number
Dave P wrote:
> On Tuesday 19 Feb 2008, Klaus Schmidinger wrote:
>
>> > remote.c:124: warning: format "%016LX" expects type "long long
>> > unsigned int", but argument 4 has type "uint64_t"
>>
>> Apparently there are macros for this, like PRId64 and such.
>> But i don't like having to write someth
On Tuesday 19 Feb 2008, Klaus Schmidinger wrote:
> > remote.c:124: warning: format "%016LX" expects type "long long
> > unsigned int", but argument 4 has type "uint64_t"
>
> Apparently there are macros for this, like PRId64 and such.
> But i don't like having to write something like
>
> int64_t
On 02/17/08 16:40, Dave P wrote:
> Compiling the new version on my 64-bit AMD processor produces the warnings
> below. I think they've probably been there for a while, I don't usually
> watch VDR compiling...
>
> # g++ -v
> Using built-in specs.
> Target: x86_64-mandriva-linux-gnu
> Configured
Compiling the new version on my 64-bit AMD processor produces the warnings
below. I think they've probably been there for a while, I don't usually
watch VDR compiling...
# g++ -v
Using built-in specs.
Target: x86_64-mandriva-linux-gnu
Configured
with: ../configure --prefix=/usr --libexecdir=/us
