Olin Lathrop wrote:

> Personally I don't like this method.  Include files shouldn't include
> other include files.  The dependencies should be published and the
> caller should include the necessary files.  That allows substitution
> of different libraries with the same interface at the program level.

I don't quite understand your argument. The advantage of include
directives in include files is exactly that you don't have to change
your code in case you want to use a different library with the same
interface.

  #include "library1.h"
  int main()
  {
    return library_function();
  }

becomes (after a library switch)

  #include "library2.h"
  int main()
  {
    return library_function();
  }

no matter what the dependencies of library1 and library2 are.

With your method, it seems to me that for a switch of libraries you'd
have to update the include directives according to the library
dependencies in each file that uses that library. I find this tiresome;
that's why I use includes inside include files. The user doesn't have to
worry about dependencies; they are included automatically.

Gerhard
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist