I just got word from my supplier that Visual Studio 2005 Pro won’t be dispatched until 10 December now, which allegedly is due to shipping delays at Microsoft and as such will affect all suppliers in the UK. Darn.
I have Express already obviously, but I’m still doing most of my work in 2002 since I can’t bear to be without my favorite plugins for too long. Let’s hope it arrives before Xmas, think of all those sad little faces on Christmas morning if Visual Studio 2005 doesn’t make it into their stockings. Santa just might end up on the business end of little Johnny’s next DDOS attack. Bless.
November 21st, 2005 at 6:19 pm
You actually just made me laugh, geek jokes are great. The problem is, it’s so true
November 23rd, 2005 at 8:40 pm
I’ve recently come across something in Visual Studio that made me cringe. I’m not sure if I’m just so anti-ms that I’m just biased or not, but perhaps you might be more level headed then I.
What it was is that when bringing in a library of code to Visual Studio when the code compiled I got a C1010 error which means that MS has a specialized syntax for handling precompiled headers. What they do is on the compile line you specify the last file to be included in any file which let’s the compiler know that it is the end of the precompiling.
Ok not so bad.
So I add in
#ifdef GOMOBILE
#include “stdafx.h”
#endif
That way it is still source compatable across other compilers.
Oh no! I get a C1020 (unexpected endif) now, after the stdafx.h.
So what I see is, MS is requiring to use their syntax, without conditional compiles in order to use precompiled headers. Otherwise you can just recompile every time you compile.
Is this another attempt to move people to MS products and away from compititions. IE, works better if it’s not compatible?
Am I over-reacting or not?
November 23rd, 2005 at 9:12 pm
Strange, I’ve never had this problem, and we use precompiled headers in OGRE. The requirements are exactly the same as previous versions (at least in Express, and I doubt it’s any different in Pro), ie that you define one header file to include all the headers (OgreStableHeaders.h) you want to precompile, you include that header in all source files, and you define a single source file (OgrePrecompiledHeaders.cpp) which does the actual precompiling. We then just #ifdef out the content of the OgreStableHeaders.h on platforms that don’t support precompilation of headers, works fine unchanged on at least 3 platforms.
This is using a manual configuration of precompiled headers which is much more manageable IMO than the automatic stdafx.h nonsense.
November 23rd, 2005 at 11:44 pm
I was under the impression that the only way to precompile headers was to use the stdafx.h nonsense.
It seems fast enough anyways, just one more glitch in the road.