> Gerhard Fiedler wrote:
> > 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.
> =

> No, it is that you don't have to know the dependencies.  However, the cho=
ice
> of library include file to use is then buried below where the application
> can control it.
> =

> Suppose the STUFF library has routines that call into the BLOBIO library.
> If you just want to use the STUFF interface and don't care that it uses
> BLOBIO, then nested include files is fine.
> =

> If you have applications that want to chose one of a set of
> BLOBIO-compatible libraries, then it's a problem.  In this case, you want
> the application to include its BLOBIO-compatible library of choice, then =
the
> STUFF library.  That doesn't work if the STUFF include file includes BLOB=
IO
> underneath.
> =


Then you can have a define that determines which BLOBIO compatible library =
you =

want to use and have one main BLOBIO include file which in turn calls the =

correct BLOBIO include file depending on the defined value. The defined val=
ue =

should be set before including the STUFF include file, perhaps even on a =

project basis. Just like UNICODE/ANSI or DEBUG/RELEASE.

/Ruben


/Ruben
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Ruben J=F6nsson
AB Liros Electronic
Box 9124, 200 39 Malm=F6, Sweden
TEL INT +46 40142078
FAX INT +46 40947388
ruben@pp.sbbs.se
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

-- =

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