I want to know will builtin dll always call other builtin dll or it depends on
winecfg setting just like other dll? Is it reliable that these dll mixed
togther? For example, the builtin gdiplus depend on and call ole dll, does the
builtin gdiplus designed to work with both builtin and native ole dll? Will
there be any incompatibilities, like different memory allocator?
regards,
question on override
question on override
On Wed, Mar 12, 2008 at 7:15 AM, bill lam <[email protected]> wrote:
away from native libraries except when you absolutely
need them.
- Dan
Depends on winecfg setting just like other dlls.I want to know will builtin dll always call other builtin dll or it depends on
winecfg setting just like other dll?
Good question. That's why we recommend stayingIs it reliable that these dll mixed
togther? For example, the builtin gdiplus depend on and call ole dll, does the
builtin gdiplus designed to work with both builtin and native ole dll? Will
there be any incompatibilities, like different memory allocator?
away from native libraries except when you absolutely
need them.
- Dan
question on override
bill lam skrev:
there's a bug; and if, in such dlls, builtin and native don't use the
same allocator, then that's a bug).
For "outer-layer" DLLs like gdiplus, this should work fine (unlessI want to know will builtin dll always call other builtin dll or it
depends on winecfg setting just like other dll? Is it reliable that
these dll mixed togther? For example, the builtin gdiplus depend on and
call ole dll, does the builtin gdiplus designed to work with both
builtin and native ole dll? Will there be any incompatibilities, like
different memory allocator?
there's a bug; and if, in such dlls, builtin and native don't use the
same allocator, then that's a bug).