David:
Whoa!
Actually, my app is not very big, and with the static linking the installation
program (InstallShield) will fit on a floppy. If I went with dynamic linking,
the footprint of my app would be smaller, but my installation program would be
much bigger because I would have to distribute the MFC and CRT dll's.
For me, fitting on a floppy is important because my app is distributed to end
users over the web, and this gives them the opportunity (which they are advised
to act on in no uncertain terms) to back up the installation program. Also, for
me, download time is more important than the time it takes for my application to
load, which is pretty minimal anyway. In any event I think chances are that my
particular users will NOT have the MFC dll's already in memory, so the load time
would actually be longer with dynamic linking.
If the time comes that my app will not fit on a floppy, I may switch to dynamic
linking. Till then, no way!
David
=============
Quote:
> > I just give thanks for the day that I decided to go with static linking
> > ...
> What, you mean increase the memory footprint and load time of your
> application with no other benefit?
> When MFC42.DLL is dynamically linked, chances are it's already in memory so
> it can just be mapped to the address space. This is fast. Loading even small
> parts of it from disk is much slower.
> --
> Dave
> http://mccabe.balliol.ox.ac.uk