Earlier today, I had a problem with a simple DirectX app - it wouldn't compile for the love of anything! It kept telling me that there were many random problems with Windows.inc, which is ludicrous as I know the include is fine... But on closer inspection, one of the includes I was using already included windows.inc and.. well... So what I did is I added a simple inclusion guard at the top and end of the include


__DEF_WINDOWS__ equ 00001h

What I'm wondering is why it wasn't done in the first place? With more complex set of includes, especially com, it get really easy to re-include an include...
Posted on 2003-07-19 02:52:44 by FearHQ