home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.std.c
- Path: sparky!uunet!elroy.jpl.nasa.gov!decwrl!deccrl!news.crl.dec.com!rdg.dec.com!uvo.dec.com!e2big.mko.dec.com!jrdzzz.jrd.dec.com!jit533.jit.dec.com!diamond
- From: diamond@jit533.jit.dec.com (Norman Diamond)
- Subject: Re: assert
- Message-ID: <BzqrDL.130@jrd.dec.com>
- Sender: usenet@jrd.dec.com (USENET News System)
- Nntp-Posting-Host: jit533.jit.dec.com
- Reply-To: diamond@jit.dec.com (Norman Diamond)
- Organization: Digital Equipment Corporation Japan , Tokyo
- References: <HBF.92Dec19163113@gandalf.uio.no> <1992Dec21.163006.8068@taumet.com> <9212211543.PN29748@LL.MIT.EDU> <1h7gc9INN8pf@chnews.intel.com>
- Date: Thu, 24 Dec 1992 02:10:33 GMT
- Lines: 19
-
- In article <1h7gc9INN8pf@chnews.intel.com> bhoughto@sedona.intel.com (Blair P. Houghton) writes:
- >In article <9212211543.PN29748@LL.MIT.EDU> lebrun@ll.mit.edu (Steven F. LeBrun) writes:
- >>I would think that standard header files
- >>including other standard header files is almost a necessity in order that
- >>standard header files may be include in any order and still keep the
- >>standard header files as simple as practical.
-
- >But--and this is a big but--the identifier definitions in a standard header
- >should be seen by the program if and only if the programmer explicitly
- >includes that header. Otherwise the programmer should expect that they are
- >not yet used.
-
- Both posters are correct, but Mr. LeBrun's opinion is not quite relevant.
- Indeed, it is almost a necessity to create broken implementations in order
- to be as simple as practical. Conforming implementations are not simple.
- --
- Norman Diamond diamond@jit081.enet.dec.com
- If this were the company's opinion, I wouldn't be allowed to post it.
- "It's been a lovely recession."
-