[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: builtin types vs. glibc types policy?
From:       Marc Espie <espie () quatramaran ! ens ! fr>
Date:       2003-02-08 16:30:51
[Download RAW message or body]

In article <200302041730.31933.nicolasg@snafu.de> you write:
>As told by others, the problem are not glibc breakages but the use of 
>non-glibc C libraries (so called portability.)
>
>As far as libc's info page, time_t seems to be portable, even if its real> type 
>can be very different. mode_t seems to be portable too.

Get out in the real world. There are lots and lots of documentation sources
out there, that go waaay beyond the meager info gnu-libc will give you
(and without the political slant, since unfortunately, the gnu documentation
is not always completely objective).

For instance, you can find the complete single unix v3 specs on
www.opengroup.org. You just need to register to get it (no strings attached,
I haven't found any).

And all three BSD have all their manpages available through their
respective websites.

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]