On Feb 17, 2008 12:49 PM, Peter Memishian <[EMAIL PROTECTED]> wrote: > > > There are many redundant include directives in some > > ON source files. This is only slightly unbeautiful, no bug. > > How have you determined that the redundancy is not just an artifact of > implementation? For instance, it's not rare for <a.h> to include <b.h> > internally as an implementation matter -- but if foo.c needs APIs from > both <a.h> and <b.h>, it should not rely on the implementation of <a.h>, > but should instead include both <a.h> and <b.h>.
Related to that, I've found a few header files where you must include a before including b -- essentially 'b' requires definitions in 'a', but itself does not include 'a'. I'd have to go back to find which ones specifically (I found them doing some porting of a network driver). Should such behavior be considered a bug? _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
