> 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