Xref: utzoo comp.os.msdos.programmer:4393 comp.windows.ms.programmer:1640 comp.lang.c++:12585 comp.lang.pascal:5949
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!think.com!barmar
From: barmar@think.com (Barry Margolin)
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.042347.22578@Think.COM>
Date: 2 Apr 91 04:23:47 GMT
References: <1991Mar30.030352.2451@borland.com> <1991Apr1.201525.19100@athena.mit.edu>
Sender: news@Think.COM
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 20

In article <1991Apr1.201525.19100@athena.mit.edu> lutwak@athena.mit.edu (Robert Lutwak) writes:
>  Now
>you expect me not only to debug your compiler for you, but you're not even 
>going to send me "confirmation, fixes, or workarounds," so that I have to
>buy the "new, improved" version.

I don't think that's what they're saying.  They're saying that sending mail
to bugs@borland.com is not the way to get personalized customer service.
Many users encounter minor problems, and simply want to inform the vendor
of it, in the hope that it will eventually be fixed (vendors don't fix bugs
they don't know about).  I do this all the time with some of my vendors,
but if if I had to make a phone call I'd never bother; but I have no
problem with firing off bug report email and forgetting about it (this
explains why I file an average of 50 bug/suggestion reports a year to
Symbolics, but have never called a VCR manufacturer).
--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar