In the end the clinching factor was the fixed intellisense support. I can live with downsides like the funky groovy colour scheme and the occasional strange behaviour of find. When you get to a certain age short term memory is not what it used to be, and I've come to rely heavily on intellisense for hinting about parameter order and types. In this regard using 2008 has been primarily an exercise in frustration, as I bash away at the "." key shouting "come on! you were there a minute ago!" at my machine.
I'm still going to be in a position to make a final build on 2008 (or even 2003) for downlevel OSs (anything pre-XP) if required, but there comes a point when continuing to support a legacy platform is counter-productive.
In other news, I've had a pretty hellish time with my old friend PF_VarString. This is the function that puts the "2" into "you get 2 rockets", and seems shockingly delicate. I've run up against it before with ports of other engines to VCPP 2008, and have fixed various problems with it already, but sooner or later it seems quite determined to misbehave. Even a straight port of an unmodified engine to VCPP 2008 has I would guess a 25% chance of blowing up in this function, and there is no apparent cause.
As a result I've had to backtrack some parts of the code to the old 1.8.3a level, so some of the memory work I've done is now lost. It seems a shame but correct behaviour is more important than elegant code.
It would be tempting to blame the memory work for this, but my opinion is naturally coloured by my previous experiences with this function.
Anyway, I'm going to bring on elements of the new stuff and see if I can pinpoint the spot at which it breaks. Overall it would be quite a coup to finally resolve what has been a problem for a good 2 years now.
Saturday, April 17, 2010
DirectQ is probably going to VCPP 2010
Posted by
mhquake
at
3:25 PM
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment