On Mon, 16 Aug 2010 16:02:17 +0100 Dave wrote: DS> On 16 August 2010 15:48, Robert Story <[email protected]> wrote: DS> > Value Hint Current output Patched output DS> > 01AA02 "1x1x1x" 1AA2 1AA2 (no change) DS> > DS> > 010203 "1x1x:1x" 12:3 12:03 (both incorrect) DS> [..] DS> The first hint is effectively no different to "1x" DS> and the second would be better written as "2x:1x"
I don't think that 1x1x and 2x are equivalent. 2579 says "the octet length: one or more decimal digits specifying the number of octets of the value to be used and formatted by this octet- specification." So 1x1x is two one byte values, where 2x is a single two byte value. So, given a value "0023", I'd expect "0023" for 1x1x, and "23" for 2x. DS> > So, if you'd like to develop a more robust fix, I'm all for it. DS> DS> Below the belt! ?? Calling my own patch non-robust? Isn't that hitting myself below the belt? :-) DS> With systems downtime tomorrow, followed by a long weekend away, DS> the chances of that are slim to nonexistent. Yeah, I know that song and dance. DS> Go ahead and apply the fix, as far as I'm concerned. DS> The new format isn't ideal, but it's definitely better than before. Yep. The vote seems to be 4+, 0 against, so I'll probably apply it tomorrow afternoon unless late objections turn up. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
