Re: A lesson for compiler warning writers

xjam@cork.CS.Berkeley.EDU (The Crossjammer)
Thu, 18 Jun 1992 18:58:37 GMT

          From comp.compilers

Related articles
A lesson for compiler warning writers Garrett.Wollman@UVM.EDU (1992-06-10)
Re: A lesson for compiler warning writers mcdaniel@adi.com (1992-06-12)
Re: A lesson for compiler warning writers tmb@arolla.idiap.ch (1992-06-17)
Re: A lesson for compiler warning writers maniattb@cs.rpi.edu (1992-06-17)
Re: A lesson for compiler warning writers stephen@estragon.uchicago.edu (1992-06-18)
Re: A lesson for compiler warning writers arnold@cc.gatech.edu (1992-06-18)
Re: A lesson for compiler warning writers xjam@cork.CS.Berkeley.EDU (1992-06-18)
Re: A lesson for compiler warning writers hays@ssd.intel.com (1992-06-18)
Re: A lesson for compiler warning writers kendall@centerline.com (1992-06-19)
Re: A lesson for compiler warning writers wicklund@intellistor.com (1992-06-18)
Re: A lesson for compiler warning writers dds@doc.imperial.ac.uk (Diomidis Spinellis) (1992-06-19)
Re: A lesson for compiler warning writers hagerman@ece.cmu.edu (1992-06-19)
Re: A lesson for compiler warning writers igor!voltaire!davidm@uunet.UU.NET (1992-06-19)
[9 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
From: xjam@cork.CS.Berkeley.EDU (The Crossjammer)
Keywords: C, linker
Organization: University of California, Berserkeley
References: <19920609091040SEB1525@MVS.draper.com> 92-06-084
Date: Thu, 18 Jun 1992 18:58:37 GMT

Arnold Robbins <arnold@cc.gatech.edu> writes:


> I have said this before, in different forums, but perhaps not as clearly.
> Rigorous compiler checking is a Good Thing, but it is not enough. No C
> compiler in the world will do cross file checking for you, only lint does
> it. If you have:


This is a touch myopic. While C has a somewhat self-defeating notion of
separate compilation it is quite easy to enforce such consistency if you
have a notion of an interface database (as John suggested). I don't
remember how industrial strength it was, but CLU had exactly such a notion
and the compiler would vigorously complain if interfaces in different
modules did not match. This idea is so simple and old that I can't believe
any other languages haven't implemented it either.


On another note, as more C vendors pick up the C++ baton, I have to
believe that this is going to be a standard feature of compilers +
environments. Make files just don't scale well enough to handle this
problem.
--
xjam@cork.Berkeley.EDU
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.