Dave Shield wrote:
I'd like to propose that we start a move to separate
such internal directives from user-level directives, by
naming them distinctively. The most obvious approach
would probably be to use a leading underscore.
So a directive such as "_usmUser" would be clearly
recognisable as an internal directive (with no
further documentation required), as distinct from
"createUser" which would be intended for admin use.
I don't like the underscore too much. Users are not necessarily familiar
with what programmers associate with an underscore. It may cause
confusion instead.
As for the general idea: why not. But it's not that the regular config
directives follow a consistent naming either. :-(
As for internal vs. regular: I'll note that some people sometimes *need*
to use those "internal" config directives (like usmUser or oldEngineID)
to implement arbitrary settings not offered by the regular tokens.
Last not least, the idea of documenting the persistent configuration
tokens separately has still not taken off. You're not trying to avoid
that, do you? ;-)
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
