Yes, libsmi is not reallytolerant to incorrect MIB modules. This could be a problem with some applications. However, if you feed only MIBs to it, that smilint does not complain about, everything should be fine.
That the line that I thought you'd take :-) Which is partly why I haven't been too bothered about reporting this yet. (Thanks for forwarding it though, David).
The problem we'll have with using libSMI in the Net-SNMP suite, is that there's an existing base of "broken" MIBs out there from old UCD-SNMP installations. Sure, we'll plaster the new release with warnings about "you *MUST* install the new (fixed) MIB files" but you know as well as I do, that there are plenty of people who won't bother reading such warnings, and end up bombarding us with complaints that it doesn't work.
Long term, the right approach is definitely to eradicate the old broken MIB files completely. But it would be desirable (from our point of view at least) if we could handle this situation in some less drastic manner than simply exiting. Even if it's just the 'exit hook' mentioned in the comment in 'printError()' - so we could get the application to spit out the message about installing the fixed MIB files.
There's no urgency about this yet, since the use of libSMI is still only within development code (and I think it's only me and Harrie that are looking at this). But I'm trying to think ahead (for once), and tackle user support problems before they bite us!
Dave
-- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.