>>>>> On Mon, 14 Apr 2008 13:57:35 +0100, "Alex Bennee" <[EMAIL PROTECTED]> >>>>> said:
AB> + typedef uint32_t oid; vs AB> + typedef u_long oid; There are a number of places that could benefit from a switch to a true int32. OIDs are only one such place (standard Integer or Integer32 datatypes being another). However, we can't make changes like that. There is a *ton* of external code out there that is built using our package as a base platform, and if they're using u_long as the data type in their code any change we make will break that. And badly, since many times pointers are passed around (otherwise it would be a simple cast and wouldn't amount to much of a problem). Generally, the ASN and relate library code should always do the right thing internally if it's passed a proper u_long where it's been expected (for a very very long time; predating most of us (including me) working on the project). -- Wes Hardaker Sparta, Inc. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
