Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!tuvie!mike
From: mike@vlsivie.tuwien.ac.at (Michael K. Gschwind)
Newsgroups: comp.sys.apollo
Subject: Re: APR's in general (long)
Message-ID: <2300@tuvie.UUCP>
Date: 5 Feb 91 10:02:16 GMT
References: <9101281715.AA16081@hwcae.cfsat.honeywell.com> <1991Jan28.190504.28488@alchemy.chem.utoronto.ca>
Sender: news@tuvie.UUCP
Organization: Vienna University of Technology
Lines: 24

In article <1991Jan28.190504.28488@alchemy.chem.utoronto.ca> system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson)) writes:
>I can't count how many APR's I have that "won't be fixed", or that the
>product is "working within specification" even though it doesn't work
>properly (who makes up the "specifications" and what good are they if
>the product still doesn't function reasonably yet meets specs?).

Sounds all too familiar. When I complained that lint breaks on ANSI-C
code and they should correct that, they answered that they use the code
they got from ATT. And that therefore, it's not their fault. They don't
have enough time to fix it, I should use the C compiler. 

I guess I should send in an APR complaining that the C compiler is not a
fully functional lint replacement, as was implied by their response. ;-)

				bye,
					mike


Michael K. Gschwind, Institute for VLSI-Design, Vienna University of Technology
mike@vlsivie.tuwien.ac.at	1-2-3-4 kick the lawsuits out the door 
mike@vlsivie.uucp		5-6-7-8 innovate don't litigate         
e182202@awituw01.bitnet		9-A-B-C interfaces should be free
Voice: (++43).1.58801 8144	D-E-F-O look and feel has got to go!
Fax:   (++43).1.569697