Larry McVoy wrote: > > Please don't listen to this. The only place you really want comments is > > a) at the top of files, describing the point of the file; > b) at the top of functions, if the purpose of the function is not obvious; > c) in line, when the code is not obvious. One other _very_ useful place: in header files. This is a place where a comment-per-line is appropriate. For example, include/linux/fs.h. Shame about `struct inode' though. - - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- RE: [OT?] Coding Style Jonathan Earle
- Re: [OT?] Coding Style Mike Harrold
- Re: [OT?] Coding Style Larry McVoy
- Re: [OT?] Coding Style Richard B. Johnson
- Re: [OT?] Coding Style Admin Mailing Lists
- Re: [OT?] Coding Style Werner Almesberger
- Re: [OT?] Coding Style Steve Underwood
- Re: [OT?] Coding Style Nicolas Noble
- Re: [OT?] Coding Style David Benfell
- Re: [OT?] Coding Style Stephen Satchell
- Re: [OT?] Coding Style Andrew Morton
- Re: [OT?] Coding Style Gregory Maxwell
- RE: [OT?] Coding Style Jonathan Earle
- RE: [OT?] Coding Style Stephen Satchell
- Re: [OT?] Coding Style Mark I Manning IV
- Re: [OT?] Coding Style Anton Altaparmakov
- Re: [OT?] Coding Style Larry McVoy
- Re: [OT?] Coding Style Stephen Satchell
- Re: [OT?] Coding Style Helge Hafting
- Re: [OT?] Coding Style Alan Olsen
- RE: [OT?] Coding Style Jonathan Earle