Re: [RFC] Use gnulib's stdint.h.

Okidoke, Here is a small status on this thread... Generally speaking, I expect all issues to be officially resolved soon. On Fri, Jun 27, 2008 at 03:31:39PM -0400, Joel Brobecker wrote: > > Boo. And if we change libdecnumber to use gnulib's version we'll > > undoubtedly break gcc. If we provide

Re: [RFC] Use gnulib's stdint.h.

Hi Bruno, > > > 2. ctype/safe-ctype conflict. For instance, cp-support.c includes > > > safe-ctype.h. But at the same time, we previously included > > > defs.h, which itself includes gnulib/stdint.h, which includes > > > which includes . > > > > > Problem #2 is a lot more probl

Re: [RFC] Use gnulib's stdint.h.

> Boo. And if we change libdecnumber to use gnulib's version we'll > undoubtedly break gcc. If we provide gstdint.h in the gdb directory > which redirects to , will libdecnumber pick it up at this > point? That's pretty ingenious. Indeed, that works, since the include order when compiling GDB fi

Re: [RFC] Use gnulib's stdint.h.

Hi, For some context, the message you were replying to is . Generally the experience we've made with gnulib is: * It's wise to include the system headers first, and the application headers after that. This minimizes the risk that

Re: [RFC] Use gnulib's stdint.h.

On Fri, Jun 27, 2008 at 02:59:07PM -0400, Joel Brobecker wrote: > There are two distinct issues that I have seen so far: > > 1. dfp.c includes libdecnumber/dpd/decimal128.h which ends up > including gstdint.h. But before we included decimal128.h, we > had already included defs.h which