Xref: utzoo comp.sys.ibm.pc:27037 comp.lang.c:17423
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!agate!ucbvax!tut.cis.ohio-state.edu!osu-cis!att!pegasus!psrc
From: psrc@pegasus.ATT.COM (Paul S. R. Chisholm)
Newsgroups: comp.sys.ibm.pc,comp.lang.c
Subject: Call for TC 2.0 bugs to give Borland
Keywords: Borland Turbo C TC 2.0
Message-ID: <2743@pegasus.ATT.COM>
Date: 4 Apr 89 22:16:22 GMT
Expires: 17 Apr 89 03:59:59 GMT
Organization: AT&T Bell Laboratories
Lines: 13

<"Would you like me to summon Data so he could offer a few dozen synonyms?">

From time to time, I have some nice communications channels into Borland,
especially with regards to calling attention to bugs.  I've forwarded one or
two TC 2.0 problems I've seen; I'm looking for more.  If you have a clear bug,
and if you can reproduce it in a small (hopefully well under a hundred lines,
and *nothing* over two hundred lines) sample program under 2.0 (tc, tcc, or
cpp), please e-mail me an explanation and the source.  I'll forward it on to
Borland.

Paul S. R. Chisholm, AT&T Bell Laboratories
att!pegasus!psrc, psrc@pegasus.att.com, AT&T Mail !psrchisholm
I'm not speaking for the company, I'm just speaking my mind.