[gme-users] change in integer limits in Constraint Manager?
Jeff Parsons
j.parsons at vanderbilt.edu
Tue Feb 7 11:37:59 CST 2006
Hi,
Thanks again, I wasn't aware of the toReal() conversion.
Jeff
> -----Original Message-----
> From: gme-users-bounces at list.isis.vanderbilt.edu
> [mailto:gme-users-bounces at list.isis.vanderbilt.edu] On Behalf
> Of Zoltan Molnar
> Sent: Tuesday, February 07, 2006 9:30 AM
> To: gme-users
> Subject: RE: [gme-users] change in integer limits in
> Constraint Manager?
>
> You could define a constraint as follows:
>
> self.oneAttr.toReal() <= 2147483647
>
> Which will detect out of range integer values on the left hand side.
>
> Hth,Zoli
>
> > -----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: Monday, February 06, 2006 7:16 PM
> > To: Steven D Baker
> > Cc: gme-users
> > Subject: RE: [gme-users] change in integer limits in
> > Constraint Manager?
> >
> >
> > Hi Steve,
> >
> > You're right, now that the constraint itself doesn't cause
> > problems, there is no value I can give to this type of
> > constant that will cause a constraint violation in GME.
> > Zoli, is there any way I can deal with this in GME?
> >
> > thanks,
> >
> > Jeff
> >
> > > -----Original Message-----
> > > From: Steven D Baker [mailto:Steven_D_Baker at raytheon.com]
> > > Sent: Monday, February 06, 2006 5:32 PM
> > > To: Jeff Parsons
> > > Subject: RE: [gme-users] change in integer limits in
> > > Constraint Manager?
> > >
> > > Hi Jeff,
> > >
> > > I hope you're doing well. Just out of curiosity, if the
> > > largest number the
> > > constraint manager can handle on the right side of the
> inequality is
> > > 2147483647, is it really possible for the statement on the
> > > left to return a
> > > value larger than that? Wouldn't the number just roll over? I
> > > didn't post
> > > this to the list - just in case I'm making some kind of
> > > idiotic mistake.
> > >
> > > Cheers,
> > >
> > > Steve
> > >
> > >
> > >
> > >
> > >
> > > "Jeff Parsons"
> > >
> > > <j.parsons at vander
> > >
> > > bilt.edu>
> > > To
> > > Sent by: "gme-users"
> > >
> > > gme-users-bounces
> > > <gme-users at list.isis.vanderbilt.edu
> > > @list.isis.vander >
> > >
> > > bilt.edu
> > > cc
> > >
> > >
> > >
> > > Subject
> > > 02/06/2006 05:58 RE: [gme-users] change
> > > in integer
> > > PM limits in Constraint
> > > Manager?
> > >
> > >
> > >
> > >
> > > Please respond to
> > >
> > > "A list for GME
> > >
> > > users to share
> > >
> > > thoughts and
> > >
> > > discuss bugs and
> > >
> > > fixes."
> > >
> > > <gme-users at list.i
> > >
> > > sis.vanderbilt.ed
> > >
> > > u>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Hi,
> > >
> > > That works, thanks!
> > >
> > > Jeff
> > >
> > > > -----Original Message-----
> > > > From: gme-users-bounces at list.isis.vanderbilt.edu
> > > > [mailto:gme-users-bounces at list.isis.vanderbilt.edu] On
> Behalf Of
> > > > Zoltan Molnar
> > > > Sent: Monday, February 06, 2006 4:32 PM
> > > > To: gme-users
> > > > Subject: RE: [gme-users] change in integer limits in Constraint
> > > > Manager?
> > > >
> > > > Jeff,
> > > >
> > > > Please use
> > > > self.oneAttr.toInteger() <= 2147483647
> > > > instead of
> > > > self.oneAttr.toInteger() < 2147483648
> > > >
> > > > respectively
> > > > Self.oneAttr.toInteger() >= -2147483648
> > > > Instead of
> > > > Self.oneAttr.toInteger() > -2147483649
> > > >
> > > > I think the latter versions are not ok because the right
> > hand side
> > > > operators were out of range. Br, Zoli
> > > >
> > > > > -----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?
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > 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?
> > > > >
> > > > > thanks,
> > > > >
> > > > > Jeff
> > > > > _______________________________________________
> > > > > gme-users mailing list
> > > > > gme-users at list.isis.vanderbilt.edu
> > > > > http://list.isis.vanderbilt.edu/mailman/listinfo/gme-users
> > > > >
> > > > _______________________________________________
> > > > gme-users mailing list
> > > > gme-users at list.isis.vanderbilt.edu
> > > > http://list.isis.vanderbilt.edu/mailman/listinfo/gme-users
> > > >
> > > _______________________________________________
> > > gme-users mailing list
> > > gme-users at list.isis.vanderbilt.edu
> > > http://list.isis.vanderbilt.edu/mailman/listinfo/gme-users
> > >
> > >
> > >
> > _______________________________________________
> > gme-users mailing list
> > gme-users at list.isis.vanderbilt.edu
> > http://list.isis.vanderbilt.edu/mailman/listinfo/gme-users
> >
> _______________________________________________
> gme-users mailing list
> gme-users at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/gme-users
>
More information about the gme-users
mailing list