On Tue, 2009-12-22 at 09:15 +0100, Bart Van Assche wrote: > > > A difficulty with the function read_config_read_octet_string() is that > it is being used for two different purposes: > 1. For reading binary strings, e.g. an engine ID. This kind of data > should be represented via a buffer pointer and buffer length, because > it can contain binary zeroes. > 2. For reading ASCII strings, e.g. usmUser::secName. This kind of data > is most conveniently represented as a zero-terminated string. > > Should we really keep a single function > read_config_read_octet_string() that is used for both reading binary > data and reading ASCII strings ? Maybe it's better to have two > functions, one for reading binary data and one for reading ASCII > strings.
I think you are right, it should be two functions. /MF ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
