C function prototyping and large projects

[Karl Heuer]

In article <432 at thirdi.UUCP> peter at thirdi.UUCP (Peter Rowell) writes:
>In article <1281 at micomvax.UUCP> ray at micomvax.UUCP (Ray Dunn) writes:
>>[Generate the prototypes automatically the first time,] then maintain the
>>information manually as you would for any other global information.
>             ^^^^^^^^
>My experience shows that manual maintenance of this type of information,
>if done incorrectly, can lead to [hard-to-find bugs].

The compiler should catch them, if the header which contains the prototype is
also included in the module that defines the function itself.

>Our solution ...  During intense development cycles there can be quite a bit
>of unnecessary reebuilds/recompiles, so we kill the dependencies and depend
>on programmer knowledge of probable side effects.

My experience shows that manual maintenance of this type of information,
if done incorrectly, can lead to hard-to-find bugs.  :-)

Karl W. Z. Heuer (ima!haddock!karl or karl at haddock.isc.com), The Walking Lint