"Ben Wing" <ben(a)666.com> writes:
i bet there's something subtle going wrong with vc 6 on windows
xp, since it's
the build os, not the run os, that matters. this makes some sense since windows
xp didn't exist when vc 6 was created.
Sadly, that sounds plausible...
it may be that all we can do is put something in PROBLEMS. i dunno.
I suppose that's reasonable, although I can imagine it would be
frustrating for people with no access to anything other than XP (it
might be worth pointing out that I've not tried XP Professional, so
that may be fine).
if you can track down further what's being miscompiled, we may
be
able to work around it. [often, it's an expression that's
miscompiled, and it's enough to simplify it using temporary
variables.]
but you have to find where the problem is -- that's the rub. if
you're patient, you could try copying over some of the .obj files
and relinking -- with a binary-search-type approach, you can maybe
find a single file that's problematic. to get farther, though, you
have to look at the assembly, which is difficult. [maybe you could
get the compiler to output assembly language and do a diff ...]
I'll keep that in mind, but frankly I don't imagine I'll have the time
in the forseeable future. The XP box isn't particularly fast, so a
rebuild (even just a relink) takes a while. Binary searching the
object modules sounds like a few days' work...
I'll report back if I ever get this done.
Thanks for the help and suggestions,
Paul.
--
This signature intentionally left blank