Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site watnot.UUCP
Path: utzoo!watmath!watnot!djfiander
From: djfiander@watnot.UUCP (David J. Fiander)
Newsgroups: net.micro.pc,net.lang.c
Subject: Re: Survey of C Compilers
Message-ID: <11897@watnot.UUCP>
Date: Tue, 22-Jul-86 10:33:23 EDT
Article-I.D.: watnot.11897
Posted: Tue Jul 22 10:33:23 1986
Date-Received: Wed, 23-Jul-86 02:31:45 EDT
References: <7975@duke.duke.UUCP> <613@looking.UUCP> <932@kontron.UUCP>
Reply-To: djfiander@watnot.UUCP (David J. Fiander)
Organization: U of Waterloo, Ontario
Lines: 29
Keywords: Microsoft support
Xref: watmath net.micro.pc:9283 net.lang.c:10003
Summary: 

>> 
>> I have used several C compilers in my projects and here are the summaries:
>> 
>> 		- Support has been reasonable for me, but I'm a beta tester.
>
>Support has been poor to useless for us.  The questions we ask usually get
>pretty useless answers, because they are usually telling us to do things
>that the manuals warned about.
>

Whenever we phoned up about a problem we were generally told that "that problem
doesn't exist" because no-one else had reported it.

One big bug that we found was not in the compiler itself but in the library.
In our product, we would try to malloc() most (if not all) of the free memory,
and after enough malloc()'s, we would start getting back pointers that pointed
into space that we already owned.  Eventually we took the malloc() and free() 
out of K&R and used that instead of the library routines.
-- 

----------

"Butterflies are free.  This means you can have as many as you want"
				-Sally Brown

    UUCP  : {allegra,ihnp4,decvax,utzoo,clyde}!watmath!watnot!djfiander
    CSNET : djfiander%watnot@waterloo.CSNET
    ARPA  : djfiander%watnot%waterloo.csnet@csnet-relay.ARPA
    BITNET: djfiande@watdcs