Re: winmm 16/32 code split

[Alexandre Julliard]

Eric Pouech  writes:
> well it depends what you want to achieve: whether you want 32 bit code
> to know
> if 16 bit procs exist or not
> I was willing to have the 16 bit code only calling thru the official 32
> bit API, so any knowledge of 16 bit entities can be removed from 32 bit
> code (which of course requires a bit more work)

Well, in general it's better to avoid having the 32-bit code know
about the 16-bit one, but there are cases where that cannot be avoided
so we can't be 100% "pure" anyway. And if sticking a 16-bit pointer in
a 32-bit structure avoids creating all sorts of ugly thunking stuff
then it's worth it.