Simon,

I've added a minimal MIB to demonstrate the issue in full. It demonstrates the issue with both the size and range.

I actually described it incorrectly in my original post. An OID with:

SYNTAX DisplayString (SIZE (0..64))

Will generate a test, but it uses the SIZE from the original DisplayString definition.

The case where no test is generated is when you have your own custom textual-convention type within your private MIB, and you add a SIZE to that.

A similar issue occurs for custom textual-conventions where the range is used instead of SIZE (for an Integer32 based type).

When the MIB compiler generates "_scalars_set_test" functions, it doesn't always parse the SIZE for textual conventions.

It does parse the SIZE for a TEXTUAL-CONVENTION that contains SIZE.
It does not parse the SIZE when added onto an existing TEXTUAL-CONVENTION.

Examples:

A working example would be a MIB object with:

SYNTAX DisplayString

Will generate the test:

if (((len >= 0) && (len <= 255)))
{
    err = SNMP_ERR_NOERROR;
}

Which is correct since it parses the SIZE for DisplayString from SNMPv2-TC.

But a MIB object with:

SYNTAX DisplayString (SIZE (0..64))

Will generate NO test, just:

err = SNMP_ERR_NOERROR;