> 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>. -- meem _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
