[gme-users] Fixing some "bugs" in GME

Douglas C. Schmidt schmidt at dre.vanderbilt.edu
Tue Apr 12 12:44:47 CDT 2005


Hi Folks,

   First and foremost, thanks very much for upgrading GME to work with
MSVC 7.1!  We look forward to the day when we can migrate all of our
ACE+TAO users from the horrible MSVC 6.0 compiler...  

   We've noticed a problem when we're building BON interpreters due to
some changes in the semantics of C++ code.  In particular, this sort of
convention:

for (<some type> i = <whatever>; ... ; ... )
{
}

. . .

for (i = <whatever>; ... ; ... )
{
}

used to be compliant in C++ (way back in the day), so MSVC 6.0 compiles
it just fine.  It's no longer spec compliant, however.  MSVC 7.1
projects are set by default to enforce the scope, but can be set to
ignore it.  There's no way at present to do this with MPC, which is the
build tool we use to generate MSVC projects, so we've been going into
GME code and fixing about a half dozen instances by changing the above
to

<some type> i;
for (i = <whatever>; ... ; ...)
{
}

. . .

for (i = <whatever>; ... ; ...)
{
}

It would be great if you folks could fix this at some point!

Thanks,

        Doug


More information about the gme-users mailing list