Home Original page

[Python-Dev] buildin vs. shared modules

Alex Martelli aleaxit at yahoo.com
Tue Oct 21 12:57:57 EDT 2003 
On Tuesday 21 October 2003 06:26 pm, Thomas Heller wrote:
   ...
> Yet another approach would be to use the delay_load feature of MSVC, it
> allows dynamic loading of the dlls at runtime, ideally without changing
> the source code.
>
> So far I have never tried that, does anyone know if this really works?

Yes, back when I was in think3 we experimented extensively as soon as
it was available (still in a beta of -- I don't recall if it was the SDK or 
VStudio 6), and except for a few specific libraries that gave some trouble
(MSVCRT.DLL and the MFC one, only -- I think because they did
something to the memory allocation mechanisms, MSVCRT having it
and MFC changing it -- perhaps it was because we were ALSO using
other memory-related tools in DLL's, e.g. leak-detectors), it always worked 
smoothly and "spread" the load, making the app startup faster.  So we
set the two DLL's that gave us trouble for load and startup and the rest
for delayed load and lived happily ever after (I don't even recall exactly
HOW we did that, it WAS years ago...).


Alex
More information about the Python-Dev mailing list