🚀 go-pugleaf

In article <729@unccvax.UUCP> cbenda@unccvax.UUCP (carl m benda) writes:
>In article <1118@csib.UUCP>, jwhitnel@csib.UUCP (Jerry Whitnell) writes:
>> >the finder and typing cc filename and with in 30 seconnds I would like to
>> >be able to double click the a.out icon.
>> 
>> I just hit cmd-R, with 15 seconds and I'm in my application.
>> >
>> >/Carl
>> >...decvax!mcnc!unccvax!cbenda
>> 
>> Jerry Whitnell
>
>My question then becomes:  Is this "application" a single file which I can
>then bring to any unsuspecting mac, see the applications icon in the finder,
>double click on the icon and then have it run in the manner in which it did
>on the system I developed it on, assuming of course similar memory and 
>other hardware configurations were taken into consideration while creating the
>application...
>/Carl

You have two options with LightspeedC.  During the development phase (Edit,
compile, link, crash and burn :-)), it does not actually make a complete
application, nor does it strip out all unnecessary routines.  This gives
it a very quick "link" to execute time.  When your application works, you
can then build a real Mac application just like any other.  

The differences between the quick-link mode and a real application are very
small, the primary one being that resources must be put in a seperate file
(which is automatically opened for you).  Of course, when you build a
real application, it automatically copies those resources over for you.

A more accurate number for the compile speed of LightspeedC is 17,000 to
21,000 lines per minute.  The former is the advertised number (Version 0.40)
on a HyperDrive, the latter was measured with the latest version (2.01) on
a DataFrame 40XP.  This number is all the more interesting since Borland's
Turbo-C on the PC claims a rate of 7,000 to 10,000 lpm!

Jerry Whitnell
Communications Solutions, Inc.