--- Robert Story <[EMAIL PROTECTED]> wrote:
> On Mon, 26 Sep 2005 15:08:37 -0700 Wes wrote: > WH> rwilcox> This is a problem for me because after > enginetime exceeds > WH> rwilcox> 65535, I begin receiving REPORT-PDUs > and then I see other > WH> rwilcox> corruption I am currently attributing > to this 4 byte vs 2 > WH> rwilcox> byte issue. > WH> > WH> Err.... Ok, you're the *very first person* to > ever report an > WH> environment where an u_int is actually only > 16bits. Unfortunately, I > WH> suspect you'll find that this is hardly the only > place that you'll run > WH> into the issue. > > Yep. You are in the same boat as the 64 bit folks. > > Knowing full well that it is a waste of my time to > do so, I proposed a mega > search/replace of all ints and longs with the new > int32_t, with cleanup for > int64_t where needed. > I am all in favor of making this modification. Is there a process in place to enact change of this magnitude? > -- > NOTE: messages sent directly to me, instead of the > lists, will be deleted > unless they are requests for paid consulting > services. > > 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
