Expanding procedure of macro contains a bug. (In message cracker) - by lightball

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.


2
0
Sign in
to vote
ID 808191 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 11/9/2013 10:17:39 PM
Access Restriction Public

Description

On Windows message cracker, I could not use HANDLE_MSG macro in visual studio 2013.
The macro is defined like this(this could be incorrect, but it does not matter in this problem):
#define HANDLE_MSG(hwnd, message, fn) case (message): HANDLE_##message(hwnd, wParam, lParam, fn)
We expect that HANDLE_MSG(hwnd, WM_CREATE, OnCreate) become HANDLE_WM_CREATE(hwnd, wParam, lParam, OnCreate), but it expanded like this:
HANDLE_0x0001(hwnd, wParam, lParam, OnCreate)
And, obviously, there is no macro or function which is named 'HANDLE_0x0001', so an error occurs.

I want to use message cracker for readability.

Thank you in advance.
p.s. My mother tongue is not English, so my text may contain some grammatical mistakes. Thank you for reading this poor text.
Sign in to post a comment.
Posted by Microsoft on 1/23/2014 at 11:45 AM
Hello lightball, thank you for reporting this issue. This issue will be fixed in an update for Visual Studio 2013.

Thanks,
Mark Roberts
Visual C++ Team
Posted by Microsoft on 1/23/2014 at 11:45 AM
Hello lightball, thank you for reporting this issue. This issue will be fixed in an update for Visual Studio 2013.

Thanks,
Mark Roberts
Visual C++ Team
Posted by EFanZh on 12/30/2013 at 5:52 AM
I've attached a source file to reproduce this problem. Hope this helps.
Posted by Microsoft on 11/14/2013 at 12:12 AM
Thanks for your feedback. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 11/13/2013 at 12:12 AM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.
Posted by Microsoft on 11/11/2013 at 11:22 PM
Hello,

Sorry for bothering. Is there any update?

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thank you!
Posted by Microsoft on 11/10/2013 at 9:46 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 11/9/2013 at 10:52 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)