On 05/17/13 10:47, Dmitry Timoshkov wrote:
Piotr Caban <piotr.ca...@gmail.com> wrote:
Just like msvcp60,msvcp70,msvcp71,msvcp80,msvcp100,msvcp110 do.
...
msvcp90 has some wine specific exports. This patch breaks other msvcpXX
dlls when native msvcp90 is installed.
Isn't that the case for other msvcp* dlls?
As far as I remember msvcp90.dll is the only one.
On the other hand there are other benefits of preferring builtin dlls
over native ones. Thanks to it the dll is tested by more users. Because
there are no reported bugs related to msvcr90 I would prefer to use
builtin dll in this case as well (actually there's one bug but it's
abandoned).
What's the point in treating only msvcp90 specially and leaving all other
msvcp* dlls prefer native versions? At least for consistency sake.
I already wrote you what's the point of treating msvcp90 differently. If
you want you can change other dlls as well but you will need to spend
time working on regressions caused by the change.
