Xref: utzoo comp.sys.amiga:16189 comp.sys.amiga.tech:60
Path: utzoo!mnetor!uunet!husc6!hao!boulder!sunybcs!bingvaxu!leah!uwmcsd1!gmwi1!marque!gryphon!crash!pnet01!haitex
From: haitex@pnet01.cts.com (Wade Bickel)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Free C Compiler?  Almost!
Message-ID: <2687@crash.cts.com>
Date: 16 Mar 88 15:36:10 GMT
Sender: news@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 46

peter@nuchat.UUCP (Peter da Silva) writes:
>In article <7626@agate.BERKELEY.EDU>, bryce@eris (Bryce Nesbitt) writes:
>> In article <> ahg@k.cc.purdue.edu (Allen Braunsdorf) writes:
>> >	Any other development tools that people think are useful.
>
>> In order:
>
>> ASDG recoverable ram disk (*if* it is legal to distribute in your manner)!!
>> MemWatch
>> morerows 
>> Conman V1.1
>
>> The first four are essential.
>
>Really? I think "arc", "uudecode", and "unshar" should be right up there.
>
>And what about "Browser 1.3"? :->/2

        Most of these are great PD programs, but do not really "need" to be
included, do they?  After all, uuencode really has nothing to do with a C
compiler, and would hopefully be included with PD communications
packages.}ir?];?>*D |Xl

        If this compiler is going to be PD, why laden the disks (or .binary)
with duplications of readily available PD software?

        Of course if it is going out on disk and there is extra space that
is a different story.


        To be honest, PD compilers make me nervous.  There OK for play, but
not for serious work.  If I run into a serious bug, I don't wan't to hear
"sorry, I'm doing spacial relations work for General Dynamics right now,
maybe in a few months...".


                                                        Thanks,

                                                                Wade.

        PS: would someone please tell me something about "Browser"?


UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!haitex
ARPA: crash!pnet01!haitex@nosc.mil
INET: haitex@pnet01.CTS.COM