This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 1/2] PowerPC - Add a new header for PowerPC specific functions
> So by this do you mean that the API is always defined in
> sys/platform/<foo>.h and particular OS implementation details (like
> #defines) are pulled from bits/<foo.h>, but that an API itself will
> never be wholely defined in bits/<foo>.h?
All I meant is that the API specification for applications to use will
never involve mention of a bits/*.h header file.
> This was suggested by Carlos O'Donell. Do you have a preference, one
> way or the other for how it should be? I know we (Power) have a
> number of functions that we're interested in providing, so in the
> interest of keeping the number of new headers down I'm in favor of
> ppc.h.
I don't have a particular opinion about whether there is one header with
many interfaces in it or many headers each with few interfaces. My point
is that the public API for a given interface must always be specified to
say that an application uses exactly one specific header file for a given
interface. We don't say, "#include <foo.h> for the foo function and
#include <bar.h> for the bar function or #include <foobar.h> for both".
For foo, either it's <foo.h> or it's <foobar.h>.
Thanks,
Roland