Unexpected errors when using --max_errors=1

[treiher]

For some otherwise correctly verified specifications, an error is shown if --max_errors=1 is set. That is the case for several example specifications. For example:

% rflx --max-errors=1 check examples/specs/ipv4.rflx 
Parsing examples/specs/ipv4.rflx
Parsing examples/specs/protocol_numbers.rflx
Processing Protocol_Numbers
Processing IPv4
examples/specs/ipv4.rflx:24:10: model: error: conflicting conditions for field "Option_Number"
examples/specs/ipv4.rflx:26:19: model: info: condition 0 (Option_Number -> Final): Option_Class = IPv4::CONTROL and Option_Number = 1
examples/specs/ipv4.rflx:28:19: model: info: condition 1 (Option_Number -> Option_Length): Option_Number > 1

[senier]

So if you chose N > 1 for --max_errors=N or leave --max-errors out it verifies?

[treiher]

Yes, exactly.

[treiher]

Fixed in version 0.12.0.