Related articles |
---|
speeding up compile times in C++ amichail@cs.toronto.edu (1995-01-26) |
Re: speeding up compile times in C++ thutt@clark.net (1995-01-26) |
Re: speeding up compile times in C++ glwinter@infi.net (1995-01-29) |
Re: speeding up compile times in C++ shankar@sgi.com (1995-02-02) |
Re: speeding up compile times in C++ glasss@ncp.gpt.co.uk (Steve Glass) (1995-02-03) |
Re: speeding up compile times in C++ thutt@clark.net (1995-02-04) |
Re: speeding up compile times in C++ rfg@rahul.net (Ronald F. Guilmette) (1995-02-04) |
Re: speeding up compile times in C++ imp@boulder.openware.com (1995-02-06) |
Re: speeding up compile times in C++ green@vizbiz.com (Anthony T. Green) (1995-02-06) |
Re: speeding up compile times in C++ shankar@sgi.com (1995-02-08) |
Re: speeding up compile times in C++ tmb@netcom.com (1995-02-12) |
Newsgroups: | comp.compilers |
From: | "Ronald F. Guilmette" <rfg@rahul.net> |
Keywords: | C++, performance |
Organization: | a2i network |
References: | 95-01-073 |
Date: | Sat, 4 Feb 1995 10:45:44 GMT |
Amir Michail <amichail@cs.toronto.edu> wrote:
>One problem with writing large C++ projects is that changing one or two
>header files often results in much of the project being recompiled. This
>is partly due to the class hierarchies and derivation.
>
>I was thinking of a way around this problem...
An excelent paper on this topic is ``Encapsulating a C++ Library'' by
Mark Linton. It appears in the 1992 USENIX C++ Conference Proceedings
(pp. 57-66; ISBN 1-880446-45-6).
If you are designing _any_ large body of C++ code, reading this paper
is an absolute must.
-- Ron Guilmette, Sunnyvale, CA
---- E-mail: rfg@segfault.us.com
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.