Subj : Re: Difference in execution using same compiler and linker options with renamed but otherwise identical source.
To   : borland.public.cpp.borlandcpp
From : DieSpammersDie.20.dwpj65
Date : Wed Aug 18 2004 11:26 pm

DieSpammersDie.20.dwpj65@spamgourmet.com (David W. Poole, Jr.) wrote in message news:<95a7672d.0408181427.f1330fb@posting.google.com>...
> Hi,
> 
> I have recently downloaded Borland's C++ command line compiler,
> version 5.5.1. It's been some time since I've used any of the Borland
> compilers, but I have a fair amount of experience with 3.0, 3.1, and
> 4.0. As a user of vi, I have always preferred to maintain my projects
> with make and command line compilers.
> 
> During the development of a small project I started recently, I
> encountered an error that I could not make heads or tails of. In the
> attempt to try troubleshooting the problem, I decided to copy the
> relevant source code to another file. In this case, I copied the
> source file PollUtil.cpp to test.cpp, without making any modifications
> to the source code. I copied and pasted the relevant lines from my
> makefile, and changed references from ?PollUtil' to ?Test'. There are
> no conditional compilation statements in my source that are based on
> the source file name.
> 
> What's driving me nuts is when I try to build the two applications,
> which are built using the same compiler and linker options, and the
> same libraries, I obtain two executables with different sizes. This is
> somewhat understandable due to issues such as debug symbols.
> 
> What isn't understandable is why the two applications execute
> differently. I am obviously targeting Win32, and there are no static
> resources to load. The app is a GUI app, although it does fire up a
> console window. Does anyone have any ideas where I can look to find
> out why these two executables run differently?

Please disregard; I've determined this to be an issue of linking the
same library twice.

.