>>>>> On Tue, 5 Oct 2004 14:02:39 -0400, [EMAIL PROTECTED] (Michael J. Slifcak) said:
[back to coders] Michael> f_fmtaddr() is proven to return a non-NULL value, for all of Michael> the transport domains embodied in snmplib/*Domain.c. Michael> However, that value is produced using a strdup() call, which Michael> could potentially return NULL when resources are constrained. When dealing with pluggable-systems (as the transports are) you *MUST* always check return values. Just because existing transports never return a NULL (except as, you point out, in memory constrained cases) doesn't mean that future or 3rd party transports won't be broken. -- "In the bathtub of history the truth is harder to hold than the soap, and much more difficult to find." -- Terry Pratchett ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
