Measuring Wine's API completeness

[Alexandre Julliard]

Dimi Paun <dimi at lattica.com> writes:

> With one exception: knowing that something is complete as far as
> documentation allows us to know is rather important. This is a
> fairly immutable point in the development of a function, and having
> reliable information about that is golden. Otherwise, one spends
> a lot of time just figuring out if something is supposed to work
> but doesn't, or it's simply an unimplemented aspect that need love.
>
> So yeah, we don't need to add "STUBBED" or "INCOMPLETE" all over
> the place. But as people working with that code know (by the nature
> of their work) that something is DONE, we should mark it as such.

The only way to know that something is done is to write a test case
for it and check the behavior against Windows. MSDN cannot be trusted,
and marking code as DONE just because it follows what happens to be in
the doc today is very misleading.

-- 
Alexandre Julliard
julliard at winehq.org