|
From: Olivier M. <om-...@ti...> - 2006-04-12 10:32:53
|
Le 12 avr. 06 =E0 12:13, Dmitry Yemanov a =E9crit : >> Why then didn't we move to the latest MSVC8 (2005)? > > Because we don't have years of experience with the new compiler and =20= > hence I > don't trust the code it produces. I had too many issues with VC7.0 =20 > to be > optimisic in this question. Well, in my personal case, the new compiler showed much more stable =20 at producing right code for commercial production applications since =20 we moved to it in november 2005. That's only 5 months experience =20 (plus the beta stage while we were testing it), but we wouldn't turn =20 back for any reason. This is the first time upgrading Microsoft =20 compiler didn't introduced bugs in our work (as it occurred when =20 moving from VC6 to VC7.1) but helped discover some lurking issues =20 (thanks to some better warnings and errors and more robust support =20 library, not to mention much improved debugger, even though more =20 resources intensive). This said, I understand your point of view. --=20 Olivier Mascia |