Colin Burgess <> email@example.com> > wrote:
Which header was that, Frank? I check into it.
like this one:
This one got is in our head branch, but only got checked in in January (sorry,
it sat around for a while), so it isn’t in the release branch. Doh!
I’ll see if I can get it in…
I also have some outstanding issues like those:
For the 6.2 tools we changed ld to search the user specified libpath for libs
that are pulled in by DT_NEEDED entries, I think this will fix this problem
firstname.lastname@example.org > wrote:
Igor Kovalenko <> Igor.Kovalenko@motorola.com> > wrote:
Which reminds me that DBL_MAX is also defined in a way which makes it
impossible to use in static initializers. That breaks some code. It is
still that way in 6.2 …
no surprise here. I have several header file problems that Colin
fixed for me and in internal CVS (back in last Sept). I don’t see
the fixes in 6.2.
it’s possible 6.2 started in another CVS branch.
Colin Burgess wrote:
There’s an error is the specification of UINT64_MAX - it should have
a ULL after it.
I’ll submit a PR for it.
Thomas <> email@example.com> > wrote:
BlankI want to use uint64_t (from stdint.h) but I cannot assign the
UINT64_MAX value to my uint64_t variable, the c++ compiler throws an error.
But checking the size of the variable gives the correct number of bytes.
Platform is Pentium III.
Count = UINT64_MAX; // produces “integer constant out of
range” error from compiler
cout << sizeof (Count) << endl; // outputs “8” for 8 bytes, 64 bits,
The largest value that can be assigned to Count is UINT32_MAX. What gives?