Xref: utzoo comp.databases:2340 comp.sys.ibm.pc:27538 comp.binaries.ibm.pc.d:2697 Path: utzoo!yunexus!maccs!cs3b3aj From: cs3b3aj@maccs.McMaster.CA (Stephen M. Dunn) Newsgroups: comp.databases,comp.sys.ibm.pc,comp.binaries.ibm.pc.d Subject: Re: Dbase compilers information Summary: Huge EXEs and slow linking Message-ID: <2463@maccs.McMaster.CA> Date: 20 Apr 89 20:33:00 GMT Article-I.D.: maccs.2463 References: <2430@cps3xx.UUCP> <3785@utastro.UUCP> <3753@silver.bacs.indiana.edu> Reply-To: cs3b3aj@maccs.UUCP (Stephen M. Dunn) Followup-To: comp.databases Organization: McMaster U., Hamilton, Ont., Can. Lines: 23 In article <3753@silver.bacs.indiana.edu> sl161011@silver.UUCP (Kevin Clendenien) writes: ... >many to be found. The other drawback is that the code generated from >linking includes all Clipper libraries, whether or not they are actually >used or not. This may just be a function of the linker supplied with >Clipper, but I've learned to live with code that is a minimum of 150K. >Clipper provides support for overlays, either external or internal, and This is not due to using PLink86; it also occurs with DOS LINK and Borland's TLINK. As for using the supplied linker, I wouldn't bother unless you need overlays; it's dreadfully slow!!! I don't have any real numbers here, but I gave up Plink long ago for the DOS linker due to speed problems, and then I switched to Tlink. I have a package that links in about 6 seconds on a 12 MHz AT clone with a 25 ms hard drive using Turbo Link; with the DOS linker, it takes about three times as long! DISCLAIMER: I have absolutely no connection with Nantucket, Microsoft or Borland other than the fact that I have used some of their products. -- ====================================================================== ! Stephen M. Dunn, cs3b3aj@maccs.McMaster.CA ! DISCLAIMER: ! ! This space left unintentionally blank - vi ! I'm only an undergrad ! ======================================================================