Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!trwind!venice!press
From: press@venice.SEDD.TRW.COM (Barry Press)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Passing data to a DLL; strange problem!
Message-ID: <1066@venice.SEDD.TRW.COM>
Date: 25 Apr 91 00:38:36 GMT
References: <1991Apr22.173022.8930@javelin.sim.es.com> <1991Apr22.185848.21897@parc.xerox.com> <1991Apr23.152726.18318@javelin.sim.es.com>
Reply-To: press@venice.sedd.trw.com (Barry Press)
Organization: TRW Systems Engineering & Development Division, Redondo Beach, CA
Lines: 24

In article <1991Apr23.152726.18318@javelin.sim.es.com> lwallace@javelin.sim.es.com (Raptor) writes:
>rybicki@parc.xerox.com (Adam Rybicki) writes:
>>Yes, I have...  There is no problem with your code.  You have two
>>variables with the same name--ParentHandle.  CodeView gets confused
>
>I used to have them named identically.  But I changed that.  I'll double-

When you go checking, consider that there may be no references in the source
code at all any more but the problem may still persist.  The reason would
be that, if you had the global declared in a header file, its existence
may have been compiled into a whole bunch of obj files.

For instance,

int foo;

in a project-wide header will put that variable into each and every object
compiled with it, and until you recompile all the files, it simply
won't go away.

This, at least, is true for MSC.  C mavens may want to flame.  Your
mileage may vary.
-- 
Barry Press                                 Internet: press@venice.sedd.trw.com