[gme-users] change in integer limits in Constraint Manager?
zolmol at isis.vanderbilt.edu
Mon Feb 6 16:31:54 CST 2006
self.oneAttr.toInteger() <= 2147483647
self.oneAttr.toInteger() < 2147483648
Self.oneAttr.toInteger() >= -2147483648
Self.oneAttr.toInteger() > -2147483649
I think the latter versions are not ok because the right hand side
operators were out of range.
> -----Original Message-----
> From: gme-users-bounces at list.isis.vanderbilt.edu
> [mailto:gme-users-bounces at list.isis.vanderbilt.edu] On Behalf
> Of Jeff Parsons
> Sent: Friday, February 03, 2006 8:09 PM
> To: gme-users
> Subject: [gme-users] change in integer limits in Constraint Manager?
> I just installed 5.9.21 and am having a problem with
> one of my constraints. Part of the constraint
> checked that an attribute value, after conversion
> to integer with toInteger() is between the limits
> of a 4-byte signed integer (I don't have the exact
> numbers at hand, but they conform to the IEEE standard,
> minus 2 billion something to plus 2 billion something).
> This worked fine with
> 4.11.10, but now the constraint always evaluates false
> even if the attribute is within range. I changed the
> values in my OCL expression to -1000 and 1000 and that
> fixed the problem - the constraint worked as expected.
> Did the GME OCL parser change after 4.11.10 in some
> way that would affect this? Does anyone know if
> limits on integer values are hard-coded into the OCL
> parser or lexer, or in the toInteger() conversion?
> gme-users mailing list
> gme-users at list.isis.vanderbilt.edu
More information about the gme-users