C / C++ / MFC

////////////////////////////////////////////////////
// in implementation of CMyListCtrl
////////////////////////////////////////////////////
  
void CMyListCtrl::OnSomething
{
    CWnd* pParent = GetParent();
    if (pParent != NULL)
        pParent->PostMessage(WM_SOMETHING, 0, 0);
}
  
  
////////////////////////////////////////////////////
// in header of CMyDlg
////////////////////////////////////////////////////
  
// ...
afx_msg void OnSomethingHappened();
// ...
  
  
////////////////////////////////////////////////////
// in implementation of CMyDlg
////////////////////////////////////////////////////
  
BEGIN_MESSAGE_MAP(CMyDlg, CDialog)
    // ...
    ON_MESSAGE(WM_SOMETHING, OnSomethingHappened)
END_MESSAGE_MAP()
  
  
void CMyDlg::OnSomethingHappened()
{
    // do something
}

1. In our old software, the memory pools were initialized when the application started up (as first action). Now, in C++, new can already be executed before the main is actually called (e.g. in the constructor of a global variable). However, we think we can solve this by performing the initialisation of the memory pools in the first call to 'new'.
   
2. In our old software, leaked memory was reported at the end. Since global variables' destructors are executed after the application has finished, we cannot report memory leaks at the end of the application, since the list will always contain memory that still needs to be deleted by the global variables' destructors.
   
3. MFC seems to have their own new and delete implementation. We aren't sure that MFC doesn't rely on some specific part of their implementation. Can we simply ignore the MFC new/delete and use our own implementation?