Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!houxm!houxz!vax135!cornell!uw-beaver!tektronix!hplabs!sri-unix!moss@BRL-VLD.ARPA From: moss@BRL-VLD.ARPA Newsgroups: net.unix Subject: Re: SDB and C programs Message-ID: <121@sri-arpa.UUCP> Date: Wed, 18-Jul-84 08:56:22 EDT Article-I.D.: sri-arpa.121 Posted: Wed Jul 18 08:56:22 1984 Date-Received: Sat, 21-Jul-84 03:25:15 EDT Lines: 18 From: "Gary S. Moss (DRXBR-VLD-V)" Sorry, can't help with SDB, but it seems to me that you should not put procedures in include files. If you are doing so because more than one program requires them, they should be archived in a library (see ar(1)). If only one program uses the procedures, than including them can only cause confusion, lint(1) for example has enough trouble determining what module and line number to report. Of course, the library should be debugged via a simple test program which is kept in the directory with the library sources to test the procedures after each version of the archive is produced. The best things to put in include files are macros, external declarations and typedefs. Global definitions and procedures should reside in '.c' files. Also, the use of '.z' as a suffix could be bad news, pack(1) uses this for output files. -- Moss.