This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3020 - wrong definition of int in op-numeric-unary-minusint1args-1
Summary: wrong definition of int in op-numeric-unary-minusint1args-1
Status: CLOSED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 0.8.6
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Carmelo Montanez
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-20 15:40 UTC by Uwe Specht
Modified: 2006-03-30 06:30 UTC (History)
1 user (show)

See Also:

Attachments

Description Uwe Specht 2006-03-20 15:40:16 UTC 
In op-numeric-unary-minusint1args-1.txt the expected result is 2147483648.
but the result of an unary operation with an int should be int.
but from datatypes 3.3.17 2147483648 is not in the range of int.
Comment 1 Carmelo Montanez 2006-03-22 16:20:18 UTC 
Hey Uwe:

Thanks for the comment.  Actually that section states
"... int is ·derived· from long by setting the value of ·maxInclusive· to be 2147483647 and ·minInclusive· to be -2147483648.  ...", which does
includes the value "-2147483648" as the minimum value.  I will marked the bug as "Assigned" for now.  Please comment further if you wish.

Thanks
Carmelo
Comment 2 Uwe Specht 2006-03-23 09:23:31 UTC 
Hey Carmelo,
i agree, but shouldn't be the result of an unary operation with an int be an int?
If not this is a misunderstanding, and the bug can be closed as invalid.
Comment 3 Carmelo Montanez 2006-03-29 19:56:48 UTC 
Uwe:

You are correct.  I was overlooking the boundary value.  I corrected the test
to use a value within the boundaries.  Thanks for the observation.  Please
close the bug if in agreement.  The changed test should be part of the
new release, which should be out later this week/early next.

Thanks,
Carmelo
Comment 4 Uwe Specht 2006-03-30 06:30:25 UTC 
Thanks for your cooperation.