C / C++ / MFC

class CPpatel
{
..
..
..
    CMySpec m_TheSpec; // Header must be included.
};

class CPpatel
{
..
..
..
    CMySpec *m_pTheSpec; // Only Forward Declaration needed.
};

Stephen Hewitt wrote:

Minimizing dependencies in a header files is a good thing.

ppatel567 wrote:

I sometimes noticed that in the header file its only written asanyheader.h=======class CMyApp;class CMySpec;

"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

class classA{<br />
classB b; //The compiler tells: What is classB? I don't know this.:(... => Error <br />
}<br />
class classB{ //Compiler interrupted:(, this isn't readed!<br />
...<br />
}

class classB; //You are telling to the compiler: wait a moment, the definition of this class will came later<br />
class classA{<br />
classB b; //The compiler tells: What is classB? I don't know how it is build, but I know that it exist  and it isn't a sintax error. So I can continue!<br />
}<br />
<br />
//The compiler tells: Yahoooo:-D, now I will know what classB is!!<br />
class classB{<br />
...<br />
}

NS17 wrote:

I think that is a last resort... !
As this control is supposed to be a common, I need to avoid such dependencies.

NS17 wrote:

So now I am planning to expose a function to allow the app to call in its PreTranslateMessage, like the RelayEvent() of ToolTip Ctrl. What's your opinion?

CArray<CPoint,CPoint> myArray;<br />
int i;<br />
<br />
// Allocate memory for at least 32 elements.<br />
myArray.SetSize(32, 128);<br />
<br />
// Add elements to the array.<br />
CPoint* pPt = (CPoint*) myArray.GetData();<br />
for (i=0;i < 32;i++,pPt++)<br />
   *pPt = CPoint(i, 2*i);<br />
<br />
// Only keep first 5 elements and free extra (unused) bytes.<br />
myArray.SetSize(5, 128);<br />
myArray.FreeExtra();