[ros-dev] Undocumented APIs

[Magnus Olsen]

Then accoring  "2. There exists a third party driver/application using the
behavior" then we can  remove whole pnp, directx, win32k, rpc, network, usb
and more. alot of api is undoc or is wrong. WHat we have left no reactos
and I agesnt it. alot of manufactor using undoc api in lowlevel and u need
implement it right.  and I do not like we have vote on it. let us work on
how to implement stuff as we have always done.

other wise we can never achive
the goal
"ReactOS aims to achieve complete binary compatibility with both
applications and device drivers"



----- Original Message ----- 
From: "Steven Edwards" <winehacker at gmail.com>
To: "ReactOS Development List" <ros-dev at reactos.org>
Sent: den 1 February 2006 00:40
Subject: Re: [ros-dev] Undocumented APIs


> I want to draw this discussion to a close and vote. Here is my proposal.
>
> A function can be implemented in ReactOS if:
>
> 1. There is documentation*
> 2. There exists a third party driver/application using the behavior
>
> If such a document* or test case does not exist it must be documented
> before it can be implemented. Clean room-reverse engineering rules
> apply.
>
> Documentation as defined as MSDN, OSR, DDK/PSDK example code, Probert
> docs, Published Book, PDB with driver or dependant test, clean room
> documentation written by some other developer than the one
> implementing the function or any documentation found via a google, msn
> or yahoo search. All documentation samples must be committed to SVN.
>
> --
> Steven Edwards - ReactOS and Wine developer
>
> "There is one thing stronger than all the armies in the world, and
> that is an idea whose time has come." - Victor Hugo
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev