On Mon, 06 Jun 2005 17:02:42 +0100 Dave wrote:
DS> What would actually break if the declaration was changed from
DS>
DS> void *cache_hint;
DS>
DS> to
DS> netsnmp_handler_args *cache_hint;
DS>
DS> If anything is currently using this field, they must be casting
DS> it to a 'netsnmp_handler_args*' anyway. That cast would become
DS> redundant, but I don't think it would actually break.
That's true. I think I was assuming a name change too.
DS> <Famous Last Words>
DS> What could possibly go wrong?
If the usage was contained to the current case (eg the flag is set), then
nothing. Making it the default, however, could, in theory, break the
almost-certainly non-existent user who was using the pointer for some other
type of hinting...
--
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
