Xref: utzoo comp.os.msdos.programmer:4405 comp.windows.ms.programmer:1659 comp.lang.c++:12614 comp.lang.pascal:5964
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!tandem!zorch!vsi1!octopus!sjsumcs!horstman
From: horstman@mathcs.sjsu.edu (Cay Horstmann)
Newsgroups: comp.os.msdos.programmer,comp.windows.ms.programmer,comp.lang.c++,comp.lang.pascal
Subject: Re: There is now a bugs@borland.com address
Message-ID: <1991Apr2.155353.2031@mathcs.sjsu.edu>
Date: 2 Apr 91 15:53:53 GMT
References: <1991Mar30.030352.2451@borland.com> <23964@well.sf.ca.us>
Organization: San Jose State University - Math/CS Dept.
Lines: 25

In article <23964@well.sf.ca.us> al@well.sf.ca.us (Alfred Fontes) writes:
>sidney@borland.com (Sidney Markowitz) writes:
>
>>I have established an email address, bugs@borland.com, to which people
>>In most cases, bugs@borland.com will not send confirmation, fixes or
>>workarounds in response to problem reports. 
>
>So why should anyone take the

Let me finish Alfred's post:
				trouble to send stuff there?

Why indeed, Sidney? Can't you guys at minimum acknowledge that you got the
stuff? That you took one of the following actions:
   (1) Ignored it
   (2) Determined it was not a bug but a feature or user error
   (3) Determined it was indeed a bug
It would be nice, of course, if in case (3) you could offer to send a fix
once it is available, but just knowing that something is indeed a bug
is pretty helpful. Since all this can be done by email, it should be fairly
low-cost (or do you expect THOUSANDS of bug reports a day? You COULD
post a list of known bugs and require that anyone submitting a new one first
check the list.)

Cay