Article View: comp.sys.ibm.pc.rt
Article #275Re: IBM bug notification/update policy
From: Chuck Karish
Date: Fri, 25 Aug 1989 16:06
Date: Fri, 25 Aug 1989 16:06
20 lines
1532 bytes
1532 bytes
In article <187@sunquest.UUCP> whm@sunquest.UUCP (Bill Mitchell) 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 -- it just uses the previous file. I reported this, >and after a couple of weeks they said that they'd filed a bug report. Against >the documentation. So, don't put functions into header files. They belong in .c files. Lint has problems finding some initializations, too, but it usually puts in a question mark after the file name, at which point the programmer has to pre-process the source to find out what's going on. >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. Chuck Karish karish@mindcraft.com (415) 493-9000 karish@forel.stanford.edu
Technical Details
Message-ID:
<4830@portia.Stanford.EDU>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!eos!shelby!portia!forel!karishReferences:
<550@pan.UUCP> <187@sunquest.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!eos!shelby!portia!forel!karish From: karish@forel.stanford.edu (Chuck Karish) Newsgroups: comp.sys.ibm.pc.rt Subject: Re: IBM bug notification/update policy Message-ID: <4830@portia.Stanford.EDU> Date: 25 Aug 89 16:06:41 GMT References: <550@pan.UUCP> <187@sunquest.UUCP> Sender: USENET News System <news@Portia.stanford.edu> Reply-To: karish@forel.stanford.edu (Chuck Karish) Organization: Mindcraft, Inc. Lines: 20