🚀 go-pugleaf

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."