> The stats do not look too good :-(. There's more stubs than I
> expected. I guess that for them to be meaningful we would really need to
> perform an analysis of which functions are really used by
> applications.
We have a PHP/MySQL database that we are hoping to release
to the world 'soon' which does this.
You can upload a dumpbin of xxx.dll and xxx.lib and it
will store the authoritative list of APIs supplied by that
version of xxx, along with ordinals, API names, and (where
available) parameter counts.
You can then edit any given API and enter subjective
data about the quality of its implementation.
You can also upload a zip file containing dumpbins of all
of the .exes and .dlls of a particular application. That
'project' can then be analyzed for external dependencies.
I'm hoping we can add a whole bunch of applications,
and then start doing some analysis to find out which APIs
are most needed, of those, which need the most help, and so on.
We have all this right now, but we're making a clean
copy (to remove confidential customer data).
Charles will put up a beta for people to check out
real soon now. Right, Charles?
Jeremy
p.s. Note that this method only provides a static analysis of
what an app really uses. You can get mislead, because
many apps do LoadLibrary/GetProcAddress and so you
miss those APIs. Also, the new COM interfaces tend
not to be caught by this approach. Still, it's a good
start.
