Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ll-xn!adelie!mirror!prism!brian
From: brian@prism.UUCP
Newsgroups: net.lang.pascal
Subject: Re: The case for Borland's Turbo Pa
Message-ID: <72100001@prism>
Date: Wed, 22-Oct-86 12:10:00 EDT
Article-I.D.: prism.72100001
Posted: Wed Oct 22 12:10:00 1986
Date-Received: Thu, 23-Oct-86 04:38:51 EDT
References: <691@looking.UUCP>
Lines: 27
Nf-ID: #R:looking.UUCP:-69100:prism:72100001:000:1253
Nf-From: prism.UUCP!brian    Oct 22 12:10:00 1986


As far as using Turbo Pascal for quick program development, I don't
think that there is anything that beats it. Sure, other compilers may
COMPILE as fast -- but, gee whiz, I think that the whole task of reading
the code from disk, compiling it, and writing an executable is the
actual COMPILE step. (Heck, my car could have a 400 horsepower engine in it,
but I don't go very fast because it only runs in first gear).

Oh, and if you think that other pascal compilers are comparable to turbo
as far as compile speed if you compile from disk, I think you are wrong.

Try compiling with source code on disk (use the M option in the compiler
to define a main file name, which INCLUDES program source on disk) and 
compile it to a .COM file - It will be quite a bit faster than Microsoft's
Pascal compiler.

That is what the development process is sometimes all about -- trying new
stuff as quickly as possible.  Then use microsoft's compiler to generate the
production code (if you think it is really necessary).

----
Brian K. Moran  brian@mirror.TMC.COM	
               {mit-eddie, ihnp4!inmet, wjh12, cca, datacube}!mirror!brian
Mirror Systems	2067 Massachusetts Avenue  Cambridge, MA, 02140
Telephone:	617-661-0777 extension 141
(((((((( * ))))))))
---