Non-strict mode has not been implemented, unfortunately. What is the
exact problem reported? If it is missing symbol imports, the solution
might be to edit the MibAnalyzer.java file a bit. Check out line 413
and onwards:
if (addMissingSmi) {
// TODO: Ugly hack that adds a "hidden" SNMPv1 SMI as the last
// import, but without any named symbols (triggering
// warnings for each symbol used).
imp = new MibImport(loader, getLocation(node),
"RFC1155-SMI", new ArrayList());
loader.scheduleLoad(imp.getName());
currentMib.addImport(imp);
imports.add(imp);
}
Feel free to extend this hack by adding other automatic MIB imports
that might have been omitted from the file by mistake.
Cheers,
/Per
2010/11/13 Валерий Протопопов <[email protected]>:
> I use mibble to parse MIB files. but in some files there is an error due to
> the fact that these files are not fully standards compliant.
>
> Q: Can I use mibble parse files in spite of the standards (non strict mode)?
> _______________________________________________
> Mibble-users mailing list
> [email protected]
> http://lists.nongnu.org/mailman/listinfo/mibble-users
>
>
_______________________________________________
Mibble-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/mibble-users
