Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!munnari.oz.au!yoyo.aarnet.edu.au!sirius.ucs.adelaide.edu.au!levels!marwk
From: marwk@levels.sait.edu.au
Newsgroups: comp.databases
Subject: Some questions about CLIPPER linking: large EXE's etc.
Message-ID: <16446.284c1c82@levels.sait.edu.au>
Date: 4 Jun 91 13:34:34 GMT
Organization: University of South Australia
Lines: 32

With CLIPPER 5.01 the EXE files for a small TBROWSE object are HHUUGGEE.

Is there a way to use the linker to cleverly only link in the subprograms
that are used?

HiTech C for the CP/M machines used to do this quite nicely.

Surely NANTUCKET modern-day programmers can do this too.

It must be me, I suppose - please just tell me which switch to use.
But if it is just a switch, why would it not be the default, and why would
anyone want to link in all the extra code when it is not used by a program?

Is this because of the ability of macro-substitution to generate calls that are
not recognised by the compiler?  If so, can this be over-ridden with a
linker switch?

If the supplied linker cannot do this, is there another product that does?

Why do people like BLINKER and why are there 3rd party linkers for CLIPPER?

Please enlighten me.

(and thanks for all the help you have given me in the past).

Ray Kennington

--
University of South Australia   | Plus ca change, plus c'est la meme chose.
P.O. Box 1                      | Ghing thien me how, ming thien gung me how.
Ingle Farm                      | Knobs, knobs everywhere,
South Australia                 |              just vary a knob to think!