On Wed, 9 Aug 2005, Vincent Béron wrote:
Changelog: LZDone is also exported by kernel32 now.
Should the same treatment be applied to the other functions too? Examples: LZStart, LZInit, GetExpandedNameA, etc. It's strange that winapi_check does not complain about them.
Does it really work to declare LZDone as exported by multiple dlls in a single comment? Should winapi_check scan the forwards and ask that we mention them all in the relevant dll documentation?
Francois Gouget fgouget@free.fr writes:
Should the same treatment be applied to the other functions too? Examples: LZStart, LZInit, GetExpandedNameA, etc. It's strange that winapi_check does not complain about them.
Does it really work to declare LZDone as exported by multiple dlls in a single comment? Should winapi_check scan the forwards and ask that we mention them all in the relevant dll documentation?
It's probably better to only mention the dll that the code is in, the documentation for a dll function shouldn't have to know about other dlls that may forward to that function.
Le mer 10/08/2005 à 05:56, Francois Gouget a écrit :
On Wed, 9 Aug 2005, Vincent Béron wrote:
Changelog: LZDone is also exported by kernel32 now.
Should the same treatment be applied to the other functions too? Examples: LZStart, LZInit, GetExpandedNameA, etc. It's strange that winapi_check does not complain about them.
I haven't had the time yet to check more closely why. There are some other warnings emitted by winapi_check which look bogus. We need to make it more intelligent and emit correct warnings if we want to use it more.
Vincent
-
Alexandre Julliard -
Francois Gouget -
Vincent Béron