About Win API Stats

[tpatko]

Hi,

I'm wondering why the following page http://www.winehq.org/winapi_stats is not automatically updated using .spec files.

It's really easy to measure implementation of a library with, for instance, the following code :

Code:
$ grep stub Projects/wine/dlls/crypt32/crypt32.spec | wc -l
40
$ grep stdcall Projects/wine/dlls/crypt32/crypt32.spec | wc -l
194
$ wc -l Projects/wine/dlls/crypt32/crypt32.spec
234 Projects/wine/dlls/crypt32/crypt32.spec



So it seems that crypt32 is ~83% (194/234) implemented.

[tpatko]

The api stat page is not up to date and how complete dlls are is not easy to guess. Just because a function is not marked as a stub in the spec file doesn't mean it is not a stub. A lot of functions are stubbed in C code. Further a large amount of functions are 'function pointers' in COM objects and for that reason also aren't counted. Only people who know dlls well can make good estimates. A while ago we thought about dropping the page altogether. Not sure why it didn't happen or else we could attempt to update it.

[tpatko]

Ideally, each time someone implements a function (or a stub) would update the stat page too.

But programmers are... programmers.
They prefer coding than documenting.

It reminds me some posts where the documentation was absent or quite old.
I think it was about mesa or X11 related stuff : there were only 2 or 3 men in the world who knew exactly how it worked and had other things to do than reading forum posts.

[tpatko]

Really it should die and be integrated into http://test.winehq.org/data/

What is the point of marking a function as implemented if it fails test cases.  None at all.

[tpatko]

You're totally right.

But I'm wondering what are the meaning of colors and numbers.
I guess red means BAD and the lowest number is GOOD...

Can someone add "how to read the table" info in the top of the page ?