Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!uakari.primate.wisc.edu!sdd.hp.com!ucsd!hub.ucsb.edu!eiffel!bertrand
From: bertrand@eiffel.UUCP (Bertrand Meyer)
Newsgroups: comp.lang.c++
Subject: Re: Problems maintaining header files
Message-ID: <486@eiffel.UUCP>
Date: 30 Jan 91 17:54:09 GMT
References: <15917@reed.UUCP> <6107@stpstn.UUCP>
Organization: Interactive Software Engineering, Santa Barbara CA
Lines: 26

From <6107@stpstn.UUCP> by lerman@stpstn.UUCP (Ken Lerman):

	> In article <15917@reed.UUCP> minar@reed.bitnet
	> (Nelson Minar,L08,x640,7776519) writes:
	> :
	> :In C, I barely managed to keep all my header files
	> straight and organized.
	> :C++ just compounds my problems.
	> ...

> Objective-C (please hold the flames down to a dull roar) uses '#import
> <foo.h>' to mean the same thing as '#include <foo.h>' except do
> nothing if the file has already been imported.  This is MUCH nicer
> than '#pragma once' and might be a useful addition to C++.

	For that matter, with Eiffel there is no need for header files
or make files of any kind. The compiler takes care of analyzing
dependencies (by analyzing the source text, which is where the
information is, and the only place where it should be) and deciding
what it needs to recompile. Of course, the language was designed
to make this possible.

	Isn't it time for the software profession to move to the
nineteen-nineties?

-- Bertrand Meyer
bertrand@eiffel.com