Path: utzoo!attcan!uunet!husc6!cmcl2!rutgers!tut.cis.ohio-state.edu!osu-cis!att!mtuxo!mtgzz!drutx!druhi!prime
From: prime@druhi.ATT.COM (Anthony Davis)
Newsgroups: comp.sys.ibm.pc
Subject: Re: dBase Procedure File "Logistics" Problem
Summary: Use Turbo C's TLINK program!
Message-ID: <3569@druhi.ATT.COM>
Date: 14 Sep 88 15:20:39 GMT
References: <1247@aucs.UUCP>
Organization: AT&T, Denver, CO
Lines: 38

In article <1247@aucs.UUCP>, peter@aucs.UUCP (Peter Steele) writes:
> I'm a fairly new dBase III+ programmer and I've run into a problem
> with procedure files that I can't seem to find a straightforward way
> around. Logically, my program consists of a main program, a procedure
> file consisting of a set of utilities used by various other procedure
> files, as well as several other procedure files each dedicated to a
> particular task. My problem is that when I'm in one of the "task"
> solving procedure files, I cannot access any of the utility routines
> because only one procedure file can be open at a time, and I have to
> call these utility routines in a variety of places (several subroutine
> calls deep). The only way I can see around this problem is either (a)
> put all the utility routines in each of the task procedure files; (b)
> put each utility routine in its own procedure file of the same name as the
> utility routine; or (c) convert to Clipper.
> ......... 
> (c) seems to be my only solution.
> This is okay because I intended to convert to Clipper at the end anyway to
> improve speed (if at all possible--I'm trying to avoid Clipper incompatible
> code in my dBase work). However, Clipper takes soooo long to link, and it's
						^^^^^^^^^^^^^^^^^^^^
Yes, this is VERY VERY true when using PLINK to link your programs. But,
Clipper supports other linkers, namely TLINK by Borland Int. Using TLINK speeds
up your link time by 80%(based on empirical studies only!! 8-) ). I've found
that linking with TLINK is extremely fast.

> no speed demon as compiler either.
     ^^^^^^^^^^^^^^^^^^^^^^^
Not so! Nantucket's new release "Summer 87" has a very *intelligent* and fast
compiler. It also does loop optimization and supports overlays. If you plan to
purchase Clipper, I'd suggest getting the latest release. Hope this helps!


#include "include/normal_disclaimer.h"

Tony Davis
AT&T Bell Labs, Denver Co.
local: druhi!prime
net:   att!druhi!prime