home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sources.wanted
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!malgudi.oar.net!chemabs!lwv26
- From: lwv26@cas.org (Larry W. Virden)
- Subject: Looking for a porting tool
- Message-ID: <1992Nov23.170651.22106@cas.org>
- Summary: tool to tell me what headers should be added
- Keywords: ansi c, posix, system 5.4, personal header identification
- Sender: usenet@cas.org
- Reply-To: lvirden@cas.org (Larry W. Virden)
- Organization: Nedriv Software and Shoe Shiners, Uninc.
- Date: Mon, 23 Nov 1992 17:03:45 GMT
- Lines: 17
-
-
- As folks move to ANSI C, POSIX, etc. they discover that while their code
- used to assemble fine, they may have neglected to include all the include
- files that technically were documented as being 'needed' by system calls,
- functions, etc.
-
- Moving to ANSI C, these include files are potentially useful as they ensure
- that arguments are promoted properly, etc.
-
- Identifying the needed headers is a headache if one is talking about hundreds,
- or thousands, of modules which need to be checked. I was wondering if
- anyone had automated the task of examining source and object files to
- identify the headers which should be included.
- --
- Larry W. Virden UUCP: osu-cis!chemabs!lvirden
- Same Mbox: BITNET: lvirden@cas INET: lvirden@cas.org
- Personal: 674 Falls Place, Reynoldsburg, OH 43068-1614
-