Thomas Weidenmueller wrote:
Casper Hornstrup wrote:
Why implement something which is not used? From a survival POV, ReactOS is better off doing what is needed instead of doing what is not needed.
Good luck. From a survival POV, we shouldn't even implement anything not documented publicly. Okay, then let's reinvent a native api to the kernel. If it turns out an application or driver really depends one one we're in deep sh... Not that I cared.
If you think a driver or application will depend on something then you can write a test program/driver and include it in the ReactOS tree. That would seem to satisfy the requirements. Black box testing is also "cleaner" (and usually faster) than clean-room reverse engineering.