On Mon, 03 Oct 2005 13:29:53 +0100 Dave wrote: DS> Replacing all int/long declarations with suitable DS> int32_t/int64_t (or unsigned equivalents) would be DS> a tedious but fairly straightforward process. The DS> difficulty is that it would blow a massive hole in DS> the principle of backward compatability. *All* DS> existing programs that use the Net-SNMP libraries DS> would need to be changed to match
I don't think that's true. The compiler generally accepts differently named types so long as they resolve to the same size and sign-ed-ness. I think the impact would be much less that you think. DS> That doesn't meant that nothing can be done in the DS> meantime. It would be perfectly possible to clean up DS> any *internal* declarations within library or agent DS> routines. Heh. All we need is a nice list of internal vs public API routines. Another item on our never-ending TODO list. ;-) -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
