Source-Changes archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: CVS commit: src/sys/fs/tmpfs



On 9/13/05, Perry E. Metzger <perry%piermont.com@localhost> wrote:
> 
> YAMAMOTO Takashi <yamt%mwd.biglobe.ne.jp@localhost> writes:
> > it makes sense for interface descriptions like vnode(9).
> > and it might make sense for high-level design explanation.
> >
> > however, in this case, what we are talking about are merely
> > implementation details.
> > IMO, having comments near the code is better,
> > especially for immature and changing code like this.
> 
> We can always do both. :)
> 
> I tend to agree that it is necessary to have the comments in the code
> as well.

Hmm... I initially had all the comments in the source files.  But while
writing the manual page, I removed them from there to avoid redundancy.
The comments left in the code are those that do not fit the manual page.
Sure, we can do both, but that means duplicates :-/

Maybe the manual page currently has too many details (like describing
each field of each structure), but if this information is not there, it is
difficult to explain general concepts.

-- 
Julio M. Merino Vidal <jmmv84%gmail.com@localhost>
http://www.livejournal.com/users/jmmv/
The NetBSD Project - http://www.NetBSD.org/



Home | Main Index | Thread Index | Old Index