On Tue, Jul 14, 2015 at 8:32 AM, Turbo Fredriksson <tu...@bayour.com> wrote:
> On Jul 14, 2015, at 8:58 AM, Bill Fenner wrote:
>
> No. As with much code that started as pre-ANSI, net-snmp uses (unsigned
> char *) to stand in for (void *).
>
>
> Ah, I see. Weird, but… :)
>
> SMI defines "Unsigned32" and "Gauge32" identically, so without a MIB
> loaded to distinguish, the command-line tool just reports Gauge32 since it
> has no way to know.
>
>
> Ok, that make sense.
>
>
> But how about the other part of the patch?
>
Now that we're shining light on this code...
Why is it correct to convert the input to unsigned, and then back to
signed, in the integer64 case? Shouldn't we use strtoll instead of
strtoull for the signed version?
Bill
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
