> Modified Files:
> 	src/usr.bin/gzip: gzip.c
> 
> Log Message:
> void functions need not call return

I am curious about this rhetoric.  I often find the return useful when
stepping through a void function in a debugger; that is, when the last
statement before the return is an assignment (for example), it gives me
the opportunity to examine the new value before the function actually
returns.  at least this is the behavior in gdb; gdb will stop on the
return (and before the stack is destroyed).

is there an advantage to removing these (besides consistency)?