Dumps the contents of your object to a CDumpContext object.

virtual void Dump( 
   CDumpContext& dc  
) const;


  • dc
    The diagnostic dump context for dumping, usually afxDump.


When you write your own class, you should override the Dump function to provide diagnostic services for yourself and other users of your class. The overridden Dump usually calls the Dump function of its base class before printing data members unique to the derived class. CObject::Dump prints the class name if your class uses the IMPLEMENT_DYNAMIC or IMPLEMENT_SERIAL macro.


Your Dump function should not print a newline character at the end of its output.

Dump calls make sense only in the Debug version of the Microsoft Foundation Class Library. You should bracket calls, function declarations, and function implementations with #ifdef _DEBUG/#endif statements for conditional compilation.

Since Dump is a const function, you are not permitted to change the object state during the dump.

The CDumpContext insertion (<<) operator calls Dump when a CObject pointer is inserted.

Dump permits only "acyclic" dumping of objects. You can dump a list of objects, for example, but if one of the objects is the list itself, you will eventually overflow the stack.


See CObList::CObList for a listing of the CAge class used in all CObject examples.

void CAge::Dump(CDumpContext &dc) const
   dc << _T("Age = ") << m_years;


Header: afx.h

See Also


CObject Class

Hierarchy Chart

Other Resources

CObject Members