Home Dashboard Directory Help
Search

Poorly picked names in rpcndr.h have a high chance of collision by Nathan Jeffords


Status: 

Closed
 as External Help for as External


2
0
Sign in
to vote
Type: Bug
ID: 775845
Opened: 1/4/2013 4:54:46 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

In the VS2012/2012.1 version of the platform SDK, there a pair of macros that are problematic.

in rpcndr.h
line 163: #define small char
line 172: #define hyper         __int64

Neither of these macros follow established naming conventions for macros. They are both surrounded by typedefs that fill similar roles, but at-least they respect scope and look-up rules. Even with proper scoping, these names are much to generic to globally make an assumption that this is what they should mean.

This is causing code that used to compile earlier versions of the compiler/platform to break.
Details
Sign in to post a comment.
Posted by Microsoft on 2/3/2013 at 5:43 PM
Hello

Thank you for your bug submission. The issue you reported appears to be a Windows issue, and we have forwarded the bug to them. We will close the bug in Connect, as they have now received it in their internal database, and they will evaluate it for the product. If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to http://support.microsoft.com or call 1-800-MICROSOFT for assistance. For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative.
Other Support links - http://support.microsoft.com/ph/14019#tab13

Thanks
Chetan Parmar
Posted by Microsoft on 1/4/2013 at 5:51 PM
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)
Sign in to post a workaround.