This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin 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: [aenchevich@shaw.ca: compile error in types.h?]


On Sun, Mar 30, 2003 at 12:30:27PM -0500, Christopher Faylor wrote:
> On Sun, Mar 30, 2003 at 07:10:18PM +0200, Corinna Vinschen wrote:
> >  Actually they should go to stdint.h, which can be
> >included from cygwin/types.h and cygwin/in.h as desired.
> 
> Shouldn't that be 'inttypes.h', which includes 'stdint.h'?  That's how
> linux seems to do it.  

Actually netinet/in.h includes stdint.h.  stdint.h contains these
definitions.  inttypes.h is... well, somehow I don't quite understand
what inttype.h is *really* good for *shrug*.

> I'll just check in the cygwin/types.h -> sys/types.h change for now.
> Personally, I don't like what seems to be the convention of defining two
> things with similar names and identical characteristics separately
> rather than having one depend on the other, though.  That seems to
> be how linux does things.

I'm not sure why newlib defines these __intXX_t types which aren't
used anywhere.

We could define our own inttypes.h and stdint.h, not depending on the
definitions in newlb.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin at cygwin dot com
Red Hat, Inc.


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