[clearview-discuss] 2008/002 Clearview UV Updates

[James Carlson]

Peter Memishian writes:
> 
>  > With respect to the implementation/documentation of this constant,
>  > I'd like to see talk (in either header comments or documentation)
>  > about either one of the above refer to the other so that someone
>  > who downloads opensolaris and goes hunting in <sys/param.h> for
>  > things to "tweak" has a clear understanding of the implications of
>  > doing so from the get go, rather than when something doesn't work.
> 
> Sure, we'll add such a comment to the header.

For what it's worth, if someone is "tweaking" #defines, then either
he's an OpenSolaris developer, in which case what he really needs in
order to do this right are _design documents_, or he's merely a
hacker, in which case he's on his own.

Either way, I don't think the concern is architectural in nature.  It
sounds more like a gate management issue that should be a broader
discussion about placing design documentation into source comments as
a "best practice" or design constraint for affected consolidations.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677