If you want me to respond David, try including my name in the
text you are including.  If you want me to even take you more
than half seriously, you might try showing some evidence of
doing more coding than sending email, so far as helping NetBSD
goes.  So far the only negative comments about comment blocks
before functions have come from people who only seem to have
a very low ratio of lines of code to email sent.

In some email I received from David Laight, sie wrote:
> 
> > But one thing I have noticed, it becomes much easier on the eye when
> > you have "drawing" when spotting function boundaries.
> 
> When do you 'spot' function boundaries?
> I either search for ^function_name or type [[ or ]] to go to
> the previous (next) function.
> 
> I have been known to put barrier comments in, usually the single line:
> /*****************************************************************/
> between separate sections of functions in a file.  But placing
> them between every pair of functions is of little or no use.
> 
> Adding comment blocks to every function just bloats the output
> of requests like 'find . -name '*.[csSh]'| xargs grep name'.
> 
> 	David
> 
> -- 
> David Laight: david@l8s.co.uk
> 
> 
> .
>