Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!lanl!jlg
From: jlg@lanl.gov (Jim Giles)
Newsgroups: comp.lang.misc
Subject: Re: Answers, Chapter 1: TeX
Message-ID: <5093@lanl.gov>
Date: 6 Nov 90 22:00:02 GMT
References: <7456:Nov620:54:4090@kramden.acf.nyu.edu>
Organization: Los Alamos Natl Lab, Los Alamos, N.M.
Lines: 17

From article <7456:Nov620:54:4090@kramden.acf.nyu.edu>, by brnstnd@kramden.acf.nyu.edu (Dan Bernstein):
> In article <5077@lanl.gov> jlg@lanl.gov (Jim Giles) writes:
> [...]
>> Not if the information in the .h file _doesn't_match_ the definition
>> of the corresponding routines in the .c file.
> 
> In which case the error will be detected at *compile time*, when the
> compiler gets around to that .c file. I stand by my statement.

Oh, now you've eliminated separate compilation.  In my experience the
main code and the libraries it calls are seldom available in source
on the same machine.  Often compiled by separate companies, possibly
in separate countries.  Mistakes happen, the .h file may not match
the code which generated the .o file (you haven't got the .c file).
I stand by my statement.

J. Giles