This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: LONG_BIT and WORD_BIT


On Nov 22 14:07, Joel Sherrill wrote:
> Hi
> 
> Linux and FreeBSD define LONG_BIT and WORD_BIT which are "CX"
> category. Newlib doesn't so I would like to discuss how to add them.
> 
> http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html
> 
> FreeBSD has them guarded like this in sys/types.h:
> 
> #if __XSI_VISIBLE || __POSIX_VISIBLE >= 200809
> #define LONG_BIT        __LONG_BIT
> #define WORD_BIT        __WORD_BIT
> #endif
> 
> 
> glibc has them in xopen_lim.h with a number of other constants.
> The include of that file has guards like this in limits.h:
> 
> #ifdef  __USE_XOPEN
> # include <bits/xopen_lim.h>
> #endif
> 
> How do folks feel about adding these? If so, what should they
> be derived from and where should they be placed?

Following Opengroup, I guess they should be in limits.h, guarded
with __POSIX_VISIBLE >= 200809.

Yaakov, what about Cygwin's limits.h?  It already defines LONG_BIT and
WORD_BIT, but neglects to guard them.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat

Attachment: signature.asc
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]