17 Oct
2009
17 Oct
'09
4:43 p.m.
On Sat, Oct 17, 2009 at 9:35 AM, Alexandre Julliard julliard@winehq.org wrote:
I think if we get a loadlibrary on an explicit private path, we should load that dll natively, even if we have a builtin dll of the same name.
No, you don't want that. There are cases of apps shipping with their own copy of system dlls, and using native in that case is wrong. It's only for apps having a non-standard version of a system dll that we may want to use native. In general we should always err on the side of using builtin.
OK, so even on an absolute path, we need to do a version check, and only use the bundled copy if it's newer than builtin? (That's what I thought you meant earlier.)