Closed cederberg closed 7 years ago
The simplest possible implementation should probably identify and categorize these three basic MIB imports. Warning could be issued when using "pre-SMIv1" or when mixing SMIv1 and SMIv2.
OBJECT-TYPE
(and more for SMIv2):enterprises
, IpAddress
and others:DisplayString
, PhysAddress
and others:Warnings should probably also be issued when using a macro def without prior import.
Closing. Fixed in 2.10.
When parsing SMIv1 files, any usage of symbols or constructs from SMIv2 should trigger a warning.
The opposite goes for SMIv2 files.