[PATCH] msvcp140: Forward __ExceptionPtr* to msvcr120

[Piotr Caban]

On 08/10/16 10:29, Nikolay Sivov wrote:
> On 10.08.2016 11:02, Piotr Caban wrote:
>> Why can't you just add forwards to msvcr120.dll in spec file?
>
> This is actually a question I've been asking myself a couple of times.
> Do we really want to load another runtime dll just to use some of its
> exports? Can it potentially break if such dependency does not exist in
> native modules?
It's possible to write an application that detects that different 
C-runtime dll is loaded. But as far as we don't know about any 
application that doesn't work because of it I would think about it as 
implementation detail. Many dlls in wine have different dependencies 
then native dlls.

In past we needed to avoid it because native dlls were not loaded when 
manifest was not present. It's not the case with msvcr120. Also I think 
I've seen an application that was loading 2 versions of C-runtime and
depending on locale being set differently in each of them (it was 
loading library linked against older C-runtime). Because of that it can 
only be done for functions that don't depend on local library settings.

The other solution for __ExceptionPtr* functions is to copy their 
implementation. I'm not sure if it's needed/better in this case.