This looks like a classic optimizer bug to me. For some reason, the
code generator has obviously decided it can used a cached version of
the data pointer for the if test rather than reloadingbut it
appears to make that decision only for the if test. It might be
interesting to try declaring
It's starting to look like upgrading to VS 2008 might be a winner for
this. I'm more willing to make this change than switch to the new
version of SysFile. Can the two version coexist on the same machine,
or do I need to uninstall 2005 first?
Rick
On Sat, Apr 25, 2009 at 11:23 PM, Mark
On Sun, Apr 26, 2009 at 4:49 AM, Rick McGuire object.r...@gmail.com wrote:
It's starting to look like upgrading to VS 2008 might be a winner for
this. I'm more willing to make this change than switch to the new
version of SysFile.
I think upgrading to VS 2008 has less potential for letting
On Sun, Apr 26, 2009 at 4:49 AM, Rick McGuire object.r...@gmail.com wrote:
It's starting to look like upgrading to VS 2008 might be a winner for
this. I'm more willing to make this change than switch to the new
version of SysFile. Can the two version coexist on the same machine,
or do I
Did you forget to paste the link?
On Sun, Apr 26, 2009 at 9:45 AM, Mark Miesfeld miesf...@gmail.com wrote:
On Sun, Apr 26, 2009 at 4:49 AM, Rick McGuire object.r...@gmail.com wrote:
It's starting to look like upgrading to VS 2008 might be a winner for
this. I'm more willing to make this
On Sun, Apr 26, 2009 at 6:58 AM, Rick McGuire object.r...@gmail.com wrote:
Did you forget to paste the link?
http://msdn.microsoft.com/en-us/library/ms246609.aspx
Didn't have my coffee yet. grin
--
Mark Miesfeld
--
On Sat, Apr 25, 2009 at 8:23 PM, Mark Miesfeld miesf...@gmail.com wrote:
In working on the SysFileSearch bug, I tracked down what seems to be a
case where the VS 2005 compiler produces wrong code and the VS 2008
produces code that works.
Good thing I said seems to be.
I was 100% wrong on
