Xref: utzoo comp.lang.c:33412 alt.religion.computers:1996 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!uupsi!sunic!news.funet.fi!funic!santra!fuug!hemuli.tik.vtt.fi!Markku.Savela From: Markku.Savela@tel.vtt.fi (Markku Savela) Newsgroups: comp.lang.c,alt.religion.computers Subject: Re: ANSI C prototypes Message-ID: <5226@hemuli.tik.vtt.fi> Date: 4 Nov 90 07:45:11 GMT References: <1005@christopher-robin.cs.bham.ac.uk> <1906@necisa.ho.necisa.oz> <1990Nov2.030556.27759@ccu.umanitoba.ca> <1990Nov3.122432.24738@ccu.umanitoba.ca> <-BV6Q16@xds13.ferranti.com> Sender: news@hemuli.tik.vtt.fi Reply-To: savela@tel.vtt.fi (Markku Savela) Followup-To: comp.lang.c Organization: Technical Research Centre of Finland Lines: 13 In-reply-to: peter@ficc.ferranti.com's message of 3 Nov 90 18:04:28 GMT In article <-BV6Q16@xds13.ferranti.com> peter@ficc.ferranti.com (Peter da Silva) writes: >> In addition to the problem of >> keeping the include files up to date, >That is the real problem. You need a tool to extract the prototypes from >a file. Beyond that, make will do the rest. Yes, but this is a bad habit. The include file should be the external specification of the module. Any changes in external specification shouldn't be so frequent, if you have the code done right. -- Markku Savela (savela@tel.vtt.fi), Technical Research Centre of Finland Telecommunications Laboratory, Otakaari 7 B, SF-02150 ESPOO, Finland