On 16/10/2007, Wes Hardaker <[EMAIL PROTECTED]> wrote: > But do realize we've just voted to not fix a bug in previous releases. > It's not a new feature. It fixes the usability of a library.
We've agreed to not fix a bug, because of a concern that the fix is likely to have greater impact than the bug itself. That's a judgement call, and may turn out to be the wrong decision. But it's not an unreasonable position to take. It might be worth annotating the "public variable" definitiions in the 5.4.x line (e.g. in TrapReceiver.xs) , to indicate that it will disappear in future releases. Similarly, maybe a mention in the 5.4.x documentation - to warn of the issue, and describe the short-term and long-term fixes. Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
