Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| Looking for header inclusion clean-up tool wprager@ca.newbridge.com (Walter Prager) (1998-08-10) |
| Re: Looking for header inclusion clean-up tool wy2lam@undergrad.math.uwaterloo.ca (Michael Lam) (1998-08-13) |
| Re: Looking for header inclusion clean-up tool dhansen@btree.com (1998-08-13) |
| Re: Looking for header inclusion clean-up tool derek@knosof.co.uk (1998-08-13) |
| Re: Looking for header inclusion clean-up tool mambuhl@tiac.net (Martin Ambuhl) (1998-08-16) |
| From: | Michael Lam <wy2lam@undergrad.math.uwaterloo.ca> |
| Newsgroups: | comp.lang.c++,comp.compilers,comp.lang.c |
| Date: | 13 Aug 1998 21:55:32 -0400 |
| Organization: | University of Waterloo |
| References: | 98-08-064 |
| Keywords: | C, tools |
Are you using the "industry-strength" header #defines? For example, if
you don't want your function prototype to be read more than once, put this
into your heaader file: (e.g. myheader.h)
#ifndef _myheader_h_
#define _myheader_h_
// the rest of your header file
#endif
It works fine for me, every time, environment-independently.
On 10 Aug 1998, Walter Prager wrote:
Has anyone out there heard of a tool which would assist in cleaning-up
header inclusion? I.e. something that goes off, works for a few hours
(days?) then produces a list of which #include's are not necessary.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.