Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!princeton!udel!burdvax!sdcrdcf!trwrb!cadovax!gryphon!richard
From: richard@gryphon.CTS.COM (Richard Sexton)
Newsgroups: comp.sys.amiga
Subject: Re: Amiga 500, digitizing, c-compilers, help!
Message-ID: <1951@gryphon.CTS.COM>
Date: Sun, 18-Oct-87 12:53:20 EDT
Article-I.D.: gryphon.1951
Posted: Sun Oct 18 12:53:20 1987
Date-Received: Mon, 19-Oct-87 03:23:58 EDT
References: <4477@spool.wisc.edu> <2529@cbmvax.UUCP>
Reply-To: richard@gryphon.CTS.COM (Richard Sexton)
Distribution: comp
Organization: Trailing Edge Technology, Redondo Beach, CA
Lines: 35
Keywords: One drive ? ONE DRIVE ??

In article <2529@cbmvax.UUCP> Paul Higginbottom  writes:
>in article <4477@spool.wisc.edu>, jojo@speedy.WISC.EDU (Jon Wesener) says:
>> 	1st, What is a good c-compiler for the Amiga.  I only have the 1
>> 	floppy at present and want one that works off 1 floppy rather well.
>
>Two drives is really helpful as you can then have a system disk and a
>source/object/binary disk.

I only have one drive, and have found the following procedure helpful.

I have 1 Meg of memory and copy the compiler, assembler, linker, includes
libraries and source into RAM:

I do my compiles in RAM:, and iff the compile was successful, 
the source is copied back to floppy.

You get the advantage of RAM: speed, with the security of knowing you
always have a good copy of your source on a floppy.

I originally had the script copy the source after every compile,
which was an unmitigated disaster. After the compiler noticed an error
it wasted my time by replacing the last good copy on the floppy with
the one that just got errors. Arrrrg !

>> jon wesener
>
>	Paul.


-- 
Richard J. Sexton
INTERNET:     richard@gryphon.CTS.COM
UUCP:         {hplabs!hp-sdd, sdcsvax, ihnp4, nosc}!crash!gryphon!richard

"It's too dark to put the keys in my ignition..."