Measuring Wine's API completeness

[James Hawkins]

On 11/12/05, Markus Amsler <markus.amsler at oribi.org> wrote:
>
> @-notation, 5 states:
>
> @unimplemented  (=STUBBED)
> @skechty
> @substantial
> @implemented    (=COMPLETE)
> @reviewed
>

The proposed method is superfluous and adds unnecessary words to the
docs and source.  You really don't get any extra information by
labeling a function as sketchy or substantial.  It's dangerous to
label a function as reviewed, because it gives the impression that the
function is absolutely complete and free of bugs.  We have a system
right now that works well.  The three states are stub, semi-stub, and
implemented, though implemented is usually denoted by the absence of
stub or semi-stub.  A stub means nothing happens at all in the
function; semi-stub means that the function does something, usually
just enough to appease some apps; implemented obviously means it's
implemented.  This is also the easiest method in that you would just
need to change c2man to parse the FIXMEs at the beginning for the word
'stub' or 'semi-stub'.  They are already in most functions, and it
would be beneficial to add them to the rest.

--
James Hawkins