cvs commit: src/sys/cam/scsi scsi_target.c src/sys/dev/mii mii.c src/sys/fs/fifofs fifo_vnops.c src/sys/gnu/ext2fs ext2_vnops.c src/sys/kern init_main.c kern_conf.c kern_descrip.c kern_event.c kern_exec.c kern_exit.c kern_fork.c kern_sig.c sys_pipe.c tty.c ...

[Garance A Drosihn]

At 11:18 PM -0400 8/15/04, Brian Fundakowski Feldman wrote:
>On Sun, Aug 15, 2004, Garance A Drosihn wrote:
>  >
>>  In some cases, such as this one, you are removing a blank line
>>  which style(9) wants to have there.  ISTR being told that if there
>>  are no local variables in a routine, there should be a blank line
>>  before the first executable statement.  Looking at the man page, I
>>  think that is shown by the example:
>>
>>  static void
>>  usage()
>>  {
>>	/* Insert an empty line if the function has no local variables. */
>
>That example actually shows there being a non-empty line where variable
>declaration would have been...  I never knew exactly what to make of it.

Yeah, the rule doesn't exactly jump out at you from the man page.
I just remember being asked to add the blank lines if there were
no local variables, so I always add them...

-- 
Garance Alistair Drosehn            =   gad at gilead.netel.rpi.edu
Senior Systems Programmer           or  gad at freebsd.org
Rensselaer Polytechnic Institute    or  drosih at rpi.edu