🚀 go-pugleaf

In article <GARYM.90Oct14143102@cognos.uucp@uunet.uu.net>, garym@cognos.uucp@uunet.uu.net (Gary Murphy) writes:
> It gets worse: the project declaration is used to identify the .SYM
> file used by all the modules.  If one file changes, the SYM may be
> changed, and this will require recompilation of all modules.  By
> poking around with a hex editor, I did find that the .SYM didn't
> always change, but unfortunately, there is no way to ensure that it
> didn't.  This almost totally cancels any benefit of using a command-line
> compiler within a MAKEFILE script.

I have written a couple of large applications in Turbo/PDC prolog, and I've
never had to recompile every module when only one was changed.  Nor does 
the need for a project file bother me, in fact it can be rather convenient.

I really appreciate the features of PDC Prolog, but while we're posting
gripes, I'd like to have an overlay linker as part of the system.  In the
mean time, some information about overlay linking would be nice.  Has 
anyone experience with overlay linking PDC Prolog modules?  Can it be done
with the MS-DOS standard linker?  I have a suspicion that the DOS linker
will only overlay link if the compiler has an overlay manager, is this so?
I'd like to purchase the PDC Prolog professional user's guide, but I'm
a poor student (sob), and I'm afraid that A$350 is just too far to
stretch at the moment.

Regards,
Euan

"When astronomers tell me that a star is so far off that its light takes a
thousand years to reach us, the magnitude of the lie seems to me inartistic"
- George Bernard Shaw