> It should be straight forward, what exactly are
> the problems you are having?
> Perhaps a showing your compiler output may give
> us a clue.

Say I have the source files x.c and y.c, and x.c
#included its header file x.h, and y.c #includes y.h.
Initially the compiler was having a field day with
errors due to the fact that x.c calls functions that
are contained within y.c.

Looking through some archived posts I learned that the
solution is to do this:

x.c #includes both x.h and y.h
y.c #includes both x.h and y.h

So that all function declarations etc are 'seen' no
matter what order in which the compiler processes
the .c files.

And to avoid multiple definition errors, both of the
header files should have guards inserted, i.e.

#ifndef _x_h
#define _x_h

...original header file code...

#endif  /* _x_h */

However, even though I have inserted the guards into my
header files as above, I am still getting multiple
definition errors relating to globals that are defined
within those header files.

I know I am doing something very daft here.

Trevor

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body