Path: utzoo!attcan!lsuc!maccs!cs4g6ag
From: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Separate overlay files w/ MSC
Summary: Plink
Message-ID: <252AD7A3.21921@maccs.dcss.mcmaster.ca>
Date: 5 Oct 89 04:25:06 GMT
References: <8000057@m.cs.uiuc.edu> <5484@ucdavis.ucdavis.edu> <1989Oct4.150541.264@esegue.segue.boston.ma.us>
Reply-To: cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn)
Organization: McMaster University, Hamilton, Ontario
Lines: 26

In article <1989Oct4.150541.264@esegue.segue.boston.ma.us> johnl@esegue.segue.boston.ma.us (John R. Levine) writes:
$In article <5484@ucdavis.ucdavis.edu> foss@iris.ucdavis.edu (Jim Alves-Foss) writes:
$>I have heard of other linkers (PLINK (?)) that let 
$>[put overlays in separate files.]
$PLINK-86 does indeed let you put overlays in separate files.  It also
[...]

   One _big_ problem with Plink - IT IS SLOW!!!  This is the price you pay
for the extra flexibility.

   I have used Plink, Microsoft Link, and Borland's Turbo Linker with
the Clipper compiler.  Generally, TLINK is 2-3 times faster than LINK,
which in turn is several times faster than PLINK86.  Of course, the
list of capabilities goes up as performance goes down, though ...

   My advice would be to use the fastest linker you can possibly
live with for development, and then only switch to Plink (or whatever)
when you absolutely have to.

DISCLAIMER:  I have no affiliation with Borland, Phoenix, or Microsoft
   other than that I have used some of their products.  Same for Nantucket.
-- 
Stephen M. Dunn                         cs4g6ag@maccs.dcss.mcmaster.ca
       <std_disclaimer.h> = "\nI'm only an undergraduate!!!\n";
**********************************************************************
TORONTO BLUE JAYS - 1989 AMERICAN LEAGUE EAST CHAMPIONS!  GO JAYS GO!!