Dave> The connection between 'table_data' and 'table_data2' Dave> is clearer than between 'table_data' and 'tdata' IMO.
Robert> For the users, distinct names are needed if the concepts/workings Robert> are different. The concepts are the same. The workings should have been, but things weren't that simple :-( Dave> And given that I've hijacked (sorry "reworked") the Dave> mib2c.table_data.conf template to use the new tdata helper Dave> instead - it felt important to emphasise that connection Robert> If the way the users deals with the data is different, Robert> should be a new conf file...... If it's just the internals Robert> that have changed, then it's debatable as to whether or not Robert> a new conf file is needed, It's just the internals, yes. Unfortunately, some of those internals used to be visible (hence this thread!) but a cleaner helper API would have allowed a backwardly compatible replacement. Robert> but the source code should be renamed regardless. Fair enough - I'm really not too bothered about the name used. It's the abstract API I'm really interested in getting right. Dave ------------------------------------------------------- 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
