> DS> Give us a chance, Robert! I'm still trying to come to terms with what
> DS> this helper does do. I'm nowhere near ready to start looking at what
> DS> it *doesn't* do! :-)
>
> I don't think we are on the same page here... I sent a command to grep the
> source for the caterpillers, put them in a line, and identify which ones you
> should pay attention to. I think that should be pretty helpful. Not sure what
> the "doesn't do" part means...
Ah - sorry. I see what you mean now.
I was mislead by the use of the token "TODO".
That's tended to be used as a marker for future work - a place where the
handling has been simplified a bit (ducking the difficult cases), and
usually denotes where we need to come back and finish things properly.
That's certainly how I use it, and how I've seen it used elsewhere.
I hadn't clicked that you were using it to track the flow of control.
Sorry for the confusion. Yes - that output looks helpful. Particularly
in conjunction with the flow section of the README file.
I'm still not clear about exactly what's going on all the time (esp. the data
mapping and setting the indexes), but it's definitely starting to come
together.
Printing out the files and highlighting the actual code helped too - you
do seem to have a tendency to over-comment (2/3 of data_access and data_get?!)
But thanks for the guidance - it has proved extremely useful.
> Hmmm.. well, the mib2c control variables are quite important!
So I'm starting to realise!
That's another difference from the previous helpers - up to now I've
just run 'mib2c -c config table' and got something I could understand.
It's taking a little while to get used to this style of micro-configuration.
You've mentioned supressing the example code, and I've spotted mention of
turning off mapping. Is there anything else that can be omitted while I'm
still learning my way around? The cache handling, perhaps?
> Which reminds me,
> I really should have made the interactive mode the default. Try running
> mib2c with -Smfd_interactive_setup=1 and see what you think..
Ummm...
$ ./mib2c -Smdf_interactive_setup=1 -c mib2c.mfd.conf myTable
no variable specified for -S flag. at ./mib2c line 96.
$ ./mib2c -S mdf_interactive_setup=1 -c mib2c.mfd.conf myTable
writing to myTable.h
| +-> Processing table myTable
writing to -
<etc, etc>
running indent on myTable_interface.c
No prompts or anything. That's working with the 5.2.pre3 code.
Am I doing something wrong?
> DS> I'm basically still identifying what can be ignored, and what is
> DS> actually useful :-)
> I tried to put as much as possilbe of the 'safe to ignore' stuff in the
> interface file.
That's the impression I got. And there doesn't seem to be much of
interest in the basic 'myTable.c' file either. I'm concentrating on
the 'data_access' and 'data_get' files for now.
Any other hints or pointers gratefully received.
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://productguide.itmanagersjournal.com/
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
