On Wed, May 4, 2011 at 4:49 PM, Robinson, Jayson A <
jayson.a.robin...@jpmchase.com> wrote:
> Can someone explain the rationalization of changing oid definition from a
> long to a 32bit integer in net-snmp 5.6.1?
>
>
>
> From pre net-snmp 5.6.1 ( We found this definition in every version
> historically ).
>
> typedef u_long oid;
>
>
>
> From net-snmp-5.6.1:
>
> typedef uint32_t oid;
>
Since the policy is to preserve the API and ABI in a branch, it's
unfortunate that this change happened in the 5.6 branch. But reverting that
change is not an option IMHO: as you can see in one of the Fedora
repositories (http://pkgs.fedoraproject.org/gitweb/?p=net-snmp.git),
Net-SNMP 5..6.1 got selected for inclusion in Fedora 15. So any attempt to
revert the aforementioned change in the 5.6 branch might cause trouble for
the Fedora project.
Bart.
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
