Re: Weeding out unwanted include files

pzola@us.oracle.com (Paul Zola)
Sat, 30 Jul 1994 21:04:03 GMT

          From comp.compilers

Related articles
Weeding out unwanted include files sriram@tcs.com (1994-07-28)
Re: Weeding out unwanted include files nandu@cs.clemson.edu (1994-07-29)
Re: Weeding out unwanted include files pzola@us.oracle.com (1994-07-30)
Re: Weeding out unwanted include files bill@amber.ssd.csd.harris.com (1994-08-02)
Re: Weeding out unwanted include files gary@Intrepid.COM (1994-08-02)
Re: Weeding out unwanted include files g9gwaigh@cdf.toronto.edu (1994-08-03)
Re: Weeding out unwanted include files zstern@adobe.com (1994-08-04)
Re: Weeding out unwanted include files steve@cegelecproj.co.uk (1994-08-04)
Re: Weeding out unwanted include files bkoehler@sol.UVic.CA (1994-08-04)
[8 later articles]
| List of all articles for this month |
Newsgroups: comp.compilers
From: pzola@us.oracle.com (Paul Zola)
Summary: FlexeLint does it
Keywords: C, tools
Organization: Oracle Corporation, Redwood Shores CA 94065
References: 94-07-090
Date: Sat, 30 Jul 1994 21:04:03 GMT

sriram@tcs.com (Sriram Srinivasan) writes:
}I want to develop a tool that finds out which include files are
}useless, so as to reduce compile time. ...
}Before I embark on this decidedly non-trivial exercise, I'd like to find
}out if someone else has implemented any such thing.


While I don't know if there is any public-domain program to do this, I do
know that (in a previous job) I used Gimpel's FlexeLint to detect unused
header files.


FlexeLint is an excellent program for detecting problems with C code. It
also has a number of non-obvious uses. (I used it as the main engine in a
shell script to generate header files from source files.) I reccomend it
highly.


Disclaimer: I have no connection with Gimpel other than as a satisfied
(former) user.
-------------------------------------------------------
Paul Zola pzola@oracle.com
Senior Technical Analyst -- Worldwide Technical Support
--


Post a followup to this message

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