[m-dev.] for review: update c_coding_guidelines.html

[schachte at cs.mu.OZ.AU]

On 29 Dec, Fergus Henderson wrote:

> w3/information/developers/c_coding_standard.html:
> 	- Change the recommended order of declarations in
> 	  header files: `#defines' should in general come
> 	  last, after function declarations, rather than before
> 	  type definitions.

It would be good to have some rationale for the recommended ordering. 

I'm curious:  why put #defines after function declarations?  The other
order, or mixed order, would seem better, since it allows function
declarations to make use of macros (not often useful, but occasionally
so); of course macro definitions can use functions either way.

-- 
Peter Schachte                     In large states public education will
mailto:schachte at cs.mu.OZ.AU        always be mediocre, for the same reason
http://www.cs.mu.oz.au/~schachte/  that in large kitchens the cooking is
PGP: finger schachte at 128.250.37.3  usually bad. -- Nietzsche 

--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------