message map macro?

Don't get it!!?? So message map just create an array?
What about macro? What is that? Can I have my own macro? is message map macro is MFC's stuffs or C++'s stuffs?

>>So message map just create an array?

Basically, yes - but this array is pretty complex :o)

>>Can I have my own macro?

Sure - a macro in general is an expression that is expanded by the precompiler, e.g. like

#define ADD(a,b) a + b

int a = 1;
int b = 2;

int c = ADD(a,b);

will result in

int c = a + b;

>>is message map macro is MFC's stuffs or C++'s stuffs?

A message map is a MFC construct and certainly isn't included in any C++ standard.

>>Can I have my own macro?
You can add message-map entries to the map.  For instance:

  ON_MESSAGE( 123456, MyFn )


This means if a message comes in and MSG.message value is 123456, then the function maned MyFn will be executed.
 
-- Dan

So, in what .h file I can find all the source that message map does? And to jkr: var c will be a global variable?

All the message map macros can be found in afxwin.h

Why this has to done with macro? Why Microsoft doesn't just use a method to this? What is the advantage to use macro?

quanghoc,
Is this question about C++ macros in general?  Or is it about how MFC uses its message mapping system?  

Please describe what you need to know.  So far you are thrashing about without direction.

-- Dan

Well, as the begin questions:
-------------------
What is the macro exactly? How is it different how a normal method/function/procedure? What C++ do with
message map macro? Is it gonna be compiled to machine code
or something?
-------------------
So far, I already understand about message map and how macro construct. But as the last couple questions:
-------------------
Why this has to done with macro? Why Microsoft doesn't just use a method to this? What is the advantage
to use macro?
-------------------
I would like to know why they created macro for! That's it. The whole thing is just the relationship between macro and message map.

I think you want to know this:
Why did Microsoft use a set of macros to implement the message-handling table.

The reason is that the table is complicated and they wanted to provide an easy way for programmers and automated tools such as the the ClassWizard to add and remove items from the table.  

For instance, which would you rather type.  This...

BEGIN_MESSAGE_MAP(CD01Dlg, CDialog)
     ON_BN_CLICKED(IDC_BUTTON1, OnButton1)
     ON_NOTIFY(LVN_BEGINDRAG, IDC_LIST1, OnBegindragList1)
END_MESSAGE_MAP()

... or this ...

const AFX_MSGMAP* PASCAL theClass::_GetBaseMessageMap()
{ return &baseClass::messageMap; }
const AFX_MSGMAP* theClass::GetMessageMap() const
{ return &theClass::messageMap; }
AFX_COMDAT AFX_DATADEF const AFX_MSGMAP theClass::messageMap =
 &theClass::_GetBaseMessageMap, &theClass::_messageEntries[0] };
AFX_COMDAT const AFX_MSGMAP_ENTRY theClass::_messageEntries[] =
{
     { WM_LBUTTONDOWN, 0, 0, 0, AfxSig_vwp,
          (AFX_PMSG)(AFX_PMSGW)(void (AFX_MSG_CALL CWnd::*)(UINT, CPoint))&OnLButtonDown
     },
     { WM_NOTIFY, (WORD)(int)wNotifyCode, (WORD)id,
          (WORD)id, AfxSig_vNMHDRpl,
          (AFX_PMSG)(void (AFX_MSG_CALL CCmdTarget::*)(NMHDR*, LRESULT*))&memberFxn
     },
     {0, 0, 0, 0, AfxSig_end, (AFX_PMSG)0 }
};

-- Dan