On Mon, 2005-04-25 at 18:49, Wes Hardaker wrote:
> Dave Shield <[EMAIL PROTECTED]> said:
>
> Dave> I knew that stepping through the table_data lists would fail,
> Dave> but that never felt to be pushed as a user-level helper.
>
> I can't think of any case, except in the emulator that we were
> providing as well, where you'd want to create a dataset table where
> all the data was being managed but you'd never look at it elsewhere.
Oh, indeed. But I'd got the general impression that
routines like 'netsnmp_table_data_set_find_column' and
'netsnmp_extract_table_data_set_column' were the intended
mechanisms for that.
> Walking through the data was the only way to view the results within
> the code (and, again, I agree I should have provided wrappers
> originally).
Fair enough.
In which case, can I suggest that we add suitable wrappers to
table_data and table_dataset now. Keep the same internals (so
not to break backward compatability), but provide a cleaner API.
Better late than never.
If we then provide the same APIs for the table_data2/table_dataset2
helpers, that should make the transition significantly easier.
Take existing table_data{,set} code, gradually tweak it to use the
APIs rather than meddling with direct pointers, and finally switch
to using the newer helper.
Can you see any problems with that?
Dave
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
