Guenther Grau <Guenther.Grau@bk.bosch.de> writes:
> Sounds great to me, except that it should be near the top, like
> on Solaris,

Uh, on what pages on Solaris is it near the top?

The pages that i've seen (on 2.6) have it in the "ATTRIBUTES" section,
always near the bottom of the manual page.  (In particular, i just
checked waitpid() and fprintf(), but that's been true for the other
manual pages that i've checked.)

Thinking about it, most uses of the manual pages won't want to know
this information; why should it be at the top?


> P.S.: And thinking about the name of the section, I even like it 
> more than Solaris' MT-Level, which might not be that clear and obvious.

Yah, "MT-level" is kinda a weird name.


FWIW, i'm not convinced that giving each separate attribute we might
want to describe its own section is a good thing.  I do kinda like the
Solaris way of describing attributes:

in the ATTRIBUTES sections of the manual page, there's a table which
tells you:

	* which architectures the interface is available on,
	* which software package provides the interface,
	* 'code set independence' (i.e. for character code sets),
	* interface stability, and lastly
	* MT-level

The tables themselves are ugly, and some of the attributes wouldn't
apply to our code, but I think overall that the idea makes sense.


cgd
-- 
Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html
Disclaimer: Not speaking for NetBSD, just expressing my own opinion.
Plug: Get your official NetBSD-1.3.2 CDROM set today! http://www.netbsd.com/