Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!noao!arizona!sunquest!whm
From: whm@sunquest.UUCP (Bill Mitchell)
Newsgroups: comp.sys.ibm.pc.rt
Subject: Re: IBM bug notification/update policy
Message-ID: <214@sunquest.UUCP>
Date: 1 Sep 89 05:15:55 GMT
References: <550@pan.UUCP> <187@sunquest.UUCP> <4830@portia.Stanford.EDU>
Organization: Sunquest Information Systems, Tucson
Lines: 26

In article <4830@portia.Stanford.EDU>, karish@forel.stanford.edu (Chuck Karish) writes:
> In article <187@sunquest.UUCP> I wrote:
> >I had the same thing happen recently with a dbx bug.  If you have a C
> >function in a #include file, dbx doesn't know to use the include file as
> >its source of source lines to display ...
> 
> So, don't put functions into header files.  They belong in .c files.
> ...
 
I agree that putting C functions in header files is non-standard, but in this
case, some code being ported from VMS has some C code in header files.  My
opinion is that if you can compile it, you should be able to debug it.

> >If that's not bad enough, they don't accept examples of bugs via electronic
> >mail, so we had to mail a floppy with a 14-line program on it.
> 
> They accept them by FAX, if you call them first so there's someone
> assigned to the problem.

For this dbx bug, I did send a FAX to the support person after the initial
contact, but she insisted on a floppy.
--------------------------------------------------------------------
Bill Mitchell				whm@sunquest.com
Sunquest Information Systems		sunquest!whm@arizona.edu
930 N. Finance Center Dr.               {arizona,uunet}!sunquest!whm
Tucson, AZ, 85710                       602-885-7700