Re: coex draft last call -- review of Section 2

>                                   .... there is nothing illegal
> about an INTEGER with no subrange or enumerations;  in fact it's
> completely equivalent to Integer32 with no subrange.

Is there anything in either RFC 2578 or IS 8824 that defines the range
of acceptable values for an (unconstrained) INTEGER syntax value?

I was under the impression that trying to assign a value of
4294967296 or above (i.e. 2^32) to an object of syntax INTEGER
would be theoretically valid - but one particular implementation
might easily choke on it, while another would be quite happy.

  By insisting that all INTEGER-based objects have an explicit
range, such inconsistencies in behaviour could be avoided.

  Or is there something I've missed that applies a 32-bit
limitation to apparently unconstrained INTEGER values?

Dave