Re: [boost] [filesystem] temp_directory_path() behavior on Windows

Subject: Re: [boost] [filesystem] temp_directory_path() behavior on Windows
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2015-02-17 07:56:41

On 17 Feb 2015 at 9:38, Olaf van der Spek wrote:

> > Have the problems with mixing binaries compiled against the DLL with
> > others compiled against the static lib been fixed in the new
> > refactor?
> 
> AFAIK DLLs should always use the DLL CRT.

Agreed. But it's a tragedy of the commons - it takes just one vendor 
to not do that in their proprietary shipped DLLs.

I can see it from their perspective - with static linkage you can 
ship a single DLL rather than one per MSVC release. And the breakage 
is better hidden than shipping a DLL which causes multiple MSVCRT 
DLLs to enter the process. But the key is the adjective "hidden".

I also look forward to when WinClang is good enough that I can ship 
my MSVC compatible DLL which was linked against libstdc++, you can 
ship yours linked against libc++, and all that is somehow supposed to 
work without incident against DLLs linked with Dinkumware. Yay ....

Niall

-- 
ned Productions Limited Consulting
http://www.nedproductions.biz/ 
http://ie.linkedin.com/in/nialldouglas/