IDL4CPP — range/min/max underspecified

A few remarks on 7.17.3:

• formatting of code in text is not done
• what is the impact of range when applied to a typedef of a basic type on all argument passing rules when that typedef is passed with a function, stored in an union or exception?
• how should min/max be implemented, shouldn't also omg::types::ranged be used?
• what should be done when min/max but also range are used as annotation?

Defer until the resolution of the related IDL RTF issue

The IDL RTF must address some of the underlying issues when applying @min, @max, @range, and @default annotations (e.g., see IDL43-89). Therefore, we are deferring the implementation of an updated mapping until the IDL RTF tackles the underlying issue.