Separate Compilation

[richard.kerry at quantel.com]

Hello,
Could somebody please either :
1. Direct me to -
or :
2. Send me -
a comprehensive explanation of separate compilation using gpc, including
examples that clearly show which bits are in different files and how the
other bits pick up their definitions. And also including any
alternate/non-standard/old-fashioned techniques that are still usable.

I am working on a very large project, developed using Oregon Pascal. The
separate compilation is done by each module (eg fred.pas) having a header
file (eg fred.def) containing all the procedures, functions, types and
constants it wishes the rest of the world to know about. All the routines
in the header are 'external'. The modules all contain their own global
variables; if any need to share, this is done by access procedures, or
records shared via pointers. There is no
module/unit/import/export/interface/implementation system involved. The
modules are compiled individually, using #include (%include in Oregon) to
pick up any external definitions and references required, and then linked.
I want to mechanically translate all these modules to gpc, so I'd prefer a
mechanism, if there is more than one available, that uses a structure as
similar as possible to the one we are currently using.

Thank you all in advance.

Richard.

PS. I apologize to anyone who has already seen this message. We've had an
email problem and I suspect my previous attempt to send this went into
hyperspace...