Re: [vos-d] Re: struggling with Windows...

On Tue, 2005-08-16 at 22:11 -0400, Peter Amstutz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tue, 16 Aug 2005, Braden McDaniel wrote: > > >> One heap - you can free memory allocated in some other module. > > > > That's the major selling point. Doing without this is giving up a

Re: [vos-d] Re: struggling with Windows...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 16 Aug 2005, Braden McDaniel wrote: One heap - you can free memory allocated in some other module. That's the major selling point. Doing without this is giving up a lot; nonetheless, I find myself considering strategies that would amelior

Re: [vos-d] Re: struggling with Windows...

res wrote: On 16.08.2005 22:24, Braden McDaniel wrote: Well that's annoying. So why bother with msvcr71.dll at all? Why not just build with /MT instead and pull in the static library? What does using the DLL runtime buy you? Disk and RAM space savings if you have multiple modules. Those a

Re: [vos-d] Re: struggling with Windows...

On 16.08.2005 22:24, Braden McDaniel wrote: > Well that's annoying. So why bother with msvcr71.dll at all? Why not > just build with /MT instead and pull in the static library? What does > using the DLL runtime buy you? Disk and RAM space savings if you have multiple modules. One heap - you can fr

[vos-d] Re: struggling with Windows...

Hugh Perkins wrote: msvcrt.dll is the old pre-.net dll, msvcr71.dll is the .net dll The import libraries have teh same name in each case (msvcrt.lib, msvcprt.lib) but point towards a differently named dll, one of those above, depending on the compiler version. This, from