Predefine Macro Problems - by Darran Rowe

Status : 

  Postponed<br /><br />
		Due to current priorities, the product team decided to postpone the resolution of this item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
0
Sign in
to vote
ID 516920 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 12/1/2009 3:06:48 AM
Access Restriction Public

Description

I know these issues have been mentioned before and they seem like they have been forgotten. Granted these only appear in the intellisense and compiled code works fine but with the recent work with the intellisense engine it would be nice to get rid of these long standing problems.

First, the __cplusplus macro is always defined even in c code.

Second the _WIN64 macro is never defined in 64 bit code.
Sign in to post a comment.
Posted by Microsoft on 5/20/2010 at 5:07 PM
Hello,

After digging in more and doing some investigations, these 2 behaviors are intentional for this release. Reasons being:
1. Our intellisense parser is a full C++ compiler, however we don't compile anything as C even if the file is C. We compile everything as C++ during our intellisense parsing. This explains why _cplusplus is defined when you have .c file open.

2. We're limited to releasing only 32bit version of our Intellisense parser for VS2010. This is a mismatch between the batch compiler and intellisense compiler. This is why _WIN64 isn't defined when you've changed your configuration to x64.

Both of these are active issues we're looking into for next release.

Thanks,
Ulzii Luvsanbat
Windows C++ Team
Posted by Darran Rowe on 4/13/2010 at 9:08 AM
This is still present in the final release of VS2010.
Posted by yecril on 3/19/2010 at 5:57 AM
Still in RC.
Posted by Microsoft on 12/4/2009 at 3:35 PM
Hello,

First of all, thank you very much for taking the time to use our product and provide feedback. As I know you are using the Beta2 version of Visual Studio 2010. Since we've shipped Beta2, we have fixed many issues in our intellisense area, as such when I try out the current build which is very close to the final RTM version of VS2010, I do see the issues are fixed. I see:
For number 1 it should be int.
For number 2 it should be long.
respectively.

Thanks,
Ulzii Luvsanbat
Windows C++ Team
Posted by Microsoft on 12/4/2009 at 1:03 AM
We were able to reproduce the issue you are seeing. We are escalating this bug to the product unit who works on that specific feature area. The product team will review this issue and make a decision on whether they will fix it or not for the next release.
Posted by Microsoft on 12/2/2009 at 2:54 AM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)