Small steps are best - they usually lead to things getting done in the end. A more NT-architecture-friendly WINE would really help us guys working on ReactOS!
- Jason
--- Eric Pouech eric.pouech@wanadoo.fr wrote:
IMHO the way WINE handles certain things is really fubar.
basically, since Wine evolves like Windows did (16 bit => win32 � la Win9x => NT infra), wine suffers from the same defaults :-(
however, I agree with you that spreading wineserver calls all over the DLLs is a bad idea IMO, the ultimate design would be to only have wineserver calls in NTDLL, but that's a long way to go... it would permit nice things as:
- portability on windows for testing the various DLLs
- (should be good for ReactOS)
- would allow to resign drop in replacement for NTDLL, like moving (part of) wineserver inside the Linux kernel
- ...
to start with, I think keeping the wineserver calls only in the holy three DLLs should be an acceptable short term target
BTW, I did extend a bit the PSAPI implementation (for some missing API) and was also upset by the calls to toolhelp for that
in short, moving to NT architecture is the way to go, but it'll need some time may be we could also create a metabug on bugzilla for this and link all known issues to this meta-bug.
A+
This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ reactos-kernel mailing list reactos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/reactos-kernel
__________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com