I find Ivor's Beginning Visual C++ 2005 certainly better than most books. He does manage to convey much of the material in a clear and easy to understand manner.

As far as the logical structure of programming in Visual C++ 2005 goes there is not much to complain about. The logical structure deals with classes, algorithms, data and their relationships.

However, there is very little on 'good practice' methods and things to watch out for regarding the 'physical' structure of your projects. Physical structure deals with spreading your projects across multiple source files and directories and how they interact. I've heard of something called the 'Pimpl Pattern' for instance, which relates to structuring your source and header files. Coverage of this part of project programming would be welcome.

Is the omission intentional? Is it something beginners should not worry about and is the phsyical structure of projects covered in more advanced books on C++?

For instance, if I want to seperate the WindowsProc function of my Windows project into a seperate source file, how would I go about this and are there hidden quirks to be mindful of when doing so?