Quote Originally Posted by lluismc View Post
but the speed of the complete compiling and linking while we made the change increased a lot.
Compilers that only knows a subset of C++ (such as the Watcom compiler) will, of course, compile the code faster. The old joke is "my compiler runs faster -- the reason is that it doesn't check for all errors...".

The C++ language has grown since DOS days, and that growth includes ANSI standardization. Compilers have to be more thorough in checking syntax, plus all the additional features that C++ has that have been built into the language. In the days of DOS, C++ compilers were merely glorified 'C' compilers, because that was all that C++ was in the late 80's and early 90's. After 1998 (ANSI standardization), those times have changed.
Is there any kind of limit on Visual C++ number of classes in the same project or any other kind of limit that should worry us? Does this limit exist in Visual Studio 8?
I'm not sure what you mean by "classes". As far as I know, you can define as many classes as you want.

I know one thing, VC 6.0 is a limited compiler. Not only is not not supported by Microsoft, third-party source code vendors dropped support for it. The reason is that many C++ source-code based libraries use templates heavily, and VC 6.0 just cannot handle the code correctly.
Is there any other way to reduce time consuming working with a big C++ project?
Check your dependencies and what files include what headers.

Regards,

Paul McKenzie