On 18:14 29/05/04, Prof A Olowofoyeku (The African Chief) wrote:
It turns out that, in order to compile a module that has its interface and implementation sections in two different files, one has to compile them this way:
gpc -c --interface-only TAttributes.int.pas gpc -c --implementation-only TAttributes.imp.pas --include TAttributes.int.pas
Have you tried using "{$include TAttributes.imp.pas}" in "TAttributes.int.pas"?
Yup; and, UIM, the second line does the same thing as what you've suggested. I was wondering why we have to include the interface section with the implementation; isn't there a way to tell GPC where to look for the implementation section(s), if we're building with (an) interface(s)--and, conversely, a way to tell GPC where to look for interface section(s)?
While I can get used to this method of compiling methods, I would really rather prefer to let the compiler look for the needed parts on its own.