On Sat, Apr 25, 2009 at 8:23 PM, Mark Miesfeld 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 this, it was not
On Sun, Apr 26, 2009 at 6:58 AM, Rick McGuire wrote:
> Did you forget to paste the link?
http://msdn.microsoft.com/en-us/library/ms246609.aspx
Didn't have my coffee yet.
--
Mark Miesfeld
--
Crystal Reports - New Free
Did you forget to paste the link?
On Sun, Apr 26, 2009 at 9:45 AM, Mark Miesfeld wrote:
> On Sun, Apr 26, 2009 at 4:49 AM, Rick McGuire 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
>> versi
On Sun, Apr 26, 2009 at 4:49 AM, Rick McGuire 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 need to uninstall 200
On Sun, Apr 26, 2009 at 4:49 AM, Rick McGuire 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 a bug
slip through
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 Miesfeld
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 t
haw, IBM Fellow
http://bit.ly/mfc
IBM UK (MP8), PO Box 31, Birmingham Road, Warwick, CV34 5JL
Mark Miesfeld wrote on 26/04/2009 04:23:04:
> Mark Miesfeld
> 26/04/2009 04:23
>
> Please respond to
> Open Object Rexx Developer Mailing List
>
> To
>
> ooRexx Dev List
>
Rick,
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.
It's bizarre, so it takes a bit to explain it. On Vista 64-bit, the
GetLine() function causes a memory exception here:
scan
