On Mon, 06 Jun 2005 10:10:14 +0100 Dave wrote:
DS> The main disadvantage of the 'cache_hint' approach is that the
DS> hint field is defined as an opaque "void*" pointer. How is a
DS> MIB developer meant to know how to use it?
Ummm, our excellent documentation? Hee hee, ha ha! Oh, I kill myself!
DS> Given that's it's only ever used as a pointer to a netsnmp_handler_args
DS> structure, why not declare it as such. Then at least the MIB developer
DS> might have a fighting chance of knowing what to do with it!
I suppose I thought it might be used for other things, base on the bits that
were set. And now I'd imagine we are stuck in the backwards compatibility
tarpit. Or do you think we can bend the rules a little in this case?
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
