C / C++ / MFC

Theres nothing wrong with nested classes. If CMySecondClass is only meaningful in the context of a CMyFirstClass object, then nesting the classes makes this clear.

However, if the second class is an implementation detail that doesn't appear in the public interface, there is another technique that you may be able to apply. In the header file that declares CMyFirstClass you simply give a forward reference to CMySecondClass:

class CMySecondClass; // forward declaration

class CMyFirstClass
{
  public:
  // public interface (CMySecondClass not mentioned)

  protected:
  CMySecondClass *m_p_instance;

  //protected or private member functions
  //which may include arguments of type
  //(CMySecondClass *) or (CMySecondClass&)
};

Now, both the declaration and implementation of CMySecondClass can be put in the implementation file
for CMyFirstClass. This provides much stronger encapsulation than a nested protected or private class, since the details of CMySecondClass aren't even visible to code that uses CMyFirstClass (other than the fact that CMySecondClass exists). With a nested protected or private class, the details of CMySecondClass are visible, but access is restricted.

Stephen C. Steel
Kerr Vayne Systems Ltd.

class CFrmTmpl : public CFormView
{
protected:
CFrmTmpl(); // protected constructor used by dynamic creation
CFrmTmpl(UINT uId); // for further derivation
...
);
 
CFrmTmpl::CFrmTmpl(UINT uId)
: CFormView(uId)
{
...
}
 
CFrm1::CFrm1()
: CFrmTmpl(CFrm1::IDD) 
{
...
)

char p_strCmd[]="200 Ok\r\n";

Send(p_strCmd, sizeof(p_strCmd), 0);