Visual C++: numeric_limits<char> min/max incorrect when using /J - by Brian J. Ehlert

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 548693 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/4/2010 10:49:59 PM
Access Restriction Public


When compiling with /J, numeric_limits<char> should return the same values as numeric_limits<unsigned char>, but does not.  Instead, the following values are given:

min: 128 (expected: 0)
max: 127 (expected: 255)
Sign in to post a comment.
Posted by Microsoft on 6/22/2010 at 1:49 PM

Thanks for reporting this bug. We've fixed it, and the fix will be available in VC11. The fix was to make numeric_limits header-only, which has the side effect of increasing performance.

If you have any further questions, feel free to E-mail me at .

Stephan T. Lavavej
Visual C++ Libraries Developer
Posted by Microsoft on 4/6/2010 at 12:20 AM
We were able to reproduce the issue you are seeing. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 4/5/2010 at 4:03 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(