[ros-dev] Tracking implementation API status

[Aleksey Bragin]

Your opinion does have a strong point.

Implemented/unimplemented were useful in the early stages, I think.  
Right now, for both Wine and ReactOS, the quality of implementation  
matters, not quantity.

How is Wine's system done, about documenting functions - where is it  
done? Source code comments? Can it be adjusted to fit ReactOS coding  
style?


WBR,
Aleksey Bragin.

On Nov 10, 2007, at 10:16 PM, Steven Edwards wrote:

> On Nov 10, 2007 4:00 AM, Aleksey Bragin <aleksey at reactos.org> wrote:
>> Hi,
>> no, I was speaking about something different.
>> Take a look - http://www.reactos.org/wiki/index.php/Coding_Style
>> there I mean this:
>
> The implemented/unimplemented tags are really worthless because what
> if the API takes 20 params and 18 of them are implemented
> and nothing known uses the other 2 params? Do you call it implemented
> or unimplemented? Its better to autogenerate the docs from the
> function comment headers. See here, I think this is a MUCH better
> system and it already works. No point in developing another.
>
> http://source.winehq.org/WineAPI/
>
> If the API does not show up in the documented API then it should be
> safe to assume its not implemented. If it is implemented and not
> documented then its a Janitorial project.
>
> -- 
> Steven Edwards
>
> "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