After dealing with all errors given the compiler and having compiled several of our modules I started looking for the compiler warnings and chasing them down. In this article and will try to show some of the warnings that I encountered and how he dealt with them.
Links:
Migration from Visual C++ 6.0 to 2005 – Part I
Migration from Visual C++ 6.0 to 2005 – Part II
Read more…
Continuing my previous article about my struggling with porting some code to VC8.0 this article shows some more of the changes we had to do in order to make our code to compile in both visual C++ 6.0 and 8.0 a.k.a. 2005.
Links:
Migration from Visual C++ 6.0 to 2005 – Part I
Migration from Visual C++ 6.0 to 2005 – Part III
Read more…
In the last few days I’ve been trying to evaluate what would take to port our applications from visual C++ 6.0 to 8.0 a.k.a. 2005. I was not overly concerned, because the projects I’m trying to convert are server side applications having no graphical user interface.
I started by converting one of the project files and trying to compile it with Visual C++2005. I started getting myriad of warnings and errors and figured that cleaning up everything will not be so easy. The first step was to get he code to compile without errors and later on clean up the warnings. I went to the project settings and disabled all warnings and tried to compile again. This time the output from the compiler was a little more manageable and here are some changes that had to be done in order to preserve compilability in both compilers during the transition period.
Links:
Migration from Visual C++ 6.0 to 2005 – Part II
Migration from Visual C++ 6.0 to 2005 – Part III
I will start with some of the very obvious ones. Read on it gets interesting…
Read more…