#2 - Mdi Win16/32 Split
steven_ed4153 at yahoo.com
Fri Jan 2 12:12:55 CST 2004
--- "Dimitrie O. Paun" <dpaun at rogers.com> wrote:
> Any idea what the status of the Win16/32 split is?
> What DLLs are still not properly split?
Its hard for me to say but most of the problems lies in user/gdi/kernel
now. The Win16/32 Cleanup is closely tied to the MS_VC+PSDK porting so
even if we remove a dependancy on a Win16 function it does not really
mean the cleanup is done. The Win32 functions may still depend on other
Wineisms. I would say overall its at 50% or more now. There are still a
few minor things to clean in shell32, comdlg32 and ole32 but I would
rate them at 80 to 90% done. Some WINE functions support the Win16 and
Win32 ANSI and Unicode case so in those cases we have to duplicate the
code and or rewrite the 32bit cases.
I think tools/winapi_check/winapi_check can check for Win16/32 Cross
Its hard to get a handle around the problems because WINE on Linux and
ReactOS differ once you get in to User, GDI, Kernel and NTDLL. There
are some cases where we can use WINE code in these modules and others
where we cant so even if we split the Win16/32 code it doesnt mean we
can make use of it.
Is a good example of a place where we have been able to import a large
chunck of WINE user32 code without a lot of nasty changes.
I would like to break with NT compatiblity a bit and implement some
WINEisms in ReactOS so when DLL seperation part 2 is done we can make
use of Winedos for our NTVDM. In the long run we may end up adding all
of the Win16 stuff back in if we ever want to create a WOW subsystem
for ReactOS. Its still going to need to be split and cleaned up though
because we dont want a dos or Win16 app to be able to crash the Win32
Do you Yahoo!?
Find out what made the Top Yahoo! Searches of 2003
More information about the wine-devel