[Gs-devel] Summary of procedure commenting discussion (re ANSIf ication)

[luke at research.canon.com.au]

On  7 Nov, L. Peter Deutsch wrote:
>  If you already have some familiarity with emacs, you might consider doing 
>  the whole thing as emacs macros with a little Lisp code.  emacs C mode 
>  already knows an awful lot about C lexical syntax, and is prepared to fix up 
>  the indentation as well. 

Sorry, I'm in the vi camp.  Actually that's another option -  a vi
macro to change them all ...  Yeah, I think I see how it could be done
that way ...

>  ansi2knr (in the Ghostscript distribution) does a fairly good job at sort-of 
>  parsing procedure definitions, but the code was never designed to be 
>  reusable. 

Righto.

BTW, I've since learned that a simple cmp of gcc object files will show
if an edit has introduced any changes, on Linux anyway.  I'd be willing
to trust the changes if gcc reported no differences.

The only untested part would be #ifdefs of other architectures, which
might not be too bad for this kind of change, I'm guessing.

luke