For Every BEGIN There Must Be an END

October 15th, 2009 by Tastic

And this is especially true for a Microsoft resource script. I just spend quite a bit of time tracking down a problem opening the resource view on a project. It would just hang indefinitely when I tried to open the resources. As it ends up, a resource definition block hidden inside of a #ifdef block was missing its END statement.

I blame Visual Studio. Visual Studio should have handled this error more gracefully than to stop responding and forcing me to kill it. They could make the resource compiler itself handle the error and report it or simply thread out the compile process so it can be stopped when I run into this type of error. Moral of the story is that when this problem happens, check each BEGIN for an END. Yay.
--hours;
In other news, I’ve moved to Kansas City and found a job programming in C++ on Window and in Visual Studio. Expect future rants to be about that for a while.

Haws & Hmms