Home/ Questions/Q 154747
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T10:02:01+00:00

I’m working on an MFC program that started way back in the VC6 days.

  • 0

I’m working on an MFC program that started way back in the VC6 days. Back then there was a class wizard that used a bunch of decorators and markup in comments to parse class files.

For example, it would insert afx_msg in front of message handlers that it maintained. It would mark a block of code with //{{AFX_MSG_MAP(TheApp) and }}AFX_MSG_MAP comments to help it find the parts of the message map it wanted to handle.

AFAIK, this isn’t needed anymore. Besides that, there were so many shortcomings with the class wizard that we had to do a lot of manual editing of these managed blocks and we never used it very often anyways.

Are there any other reasons to keep using afx_msg and its ilk?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. afx_msg still exists but has always been purely informative. A decorator as you put it. It’s always been #defined as an empty string.

    The {{ and }} markers are no longer needed since VS2003: VS is now smart enough to put things in the right place without having to rely on these markers. You’ll notice that VS2003+ no longer includes these lines in the projects it creates.

    • 0