complicated applications without a clear understanding of how the program works. Similarly, many programmers are able to tackle various Windows messages using the message maps. However, when it comes to knowing how a message gets transformed into a call to a message handler there is utter confusion. We think that it is imperative to understand the working of the VC++ program and the message maps before we can venture into advanced VC++ topics. Towards this end we would write a simple program that displays a message in a window. Then we would examine in detail the working of this program. Here is the program\u2026
myframe *p ;
p = new myframe ;
m_pMainWnd = p ;
CPaintDC d ( this ) ;
d.TextOut ( 50, 50, "Hello", 5 ) ;
We are not bound by any rule to do so. However, we are bound by tradition. Among C++ programmers it is a tradition to write the class declarations in.h files and class implementations in.cpp files. We too would follow this strategy throughout this book. For small programs this might appear to be an overkill. But in large programs containing numerous classes it is worthwhile to give each class its own.h and.cpp files. The same convention has been followed while storing the files on the CD accompanying this book.
Now bringing you back...
Does that email address look wrong? Try again with a different email.
This action might not be possible to undo. Are you sure you want to continue?