Rémi Assailly remi.assailly@free.fr writes:
--- include/wine/library.h 2005-01-07 19:41:26.000000000 +0100 +++ include/wine/library.h 2005-01-07 19:49:41.389057824 +0100 @@ -42,6 +42,7 @@ extern void *wine_dlopen( const char *filename, int flag, char *error, int errorsize ); extern void *wine_dlsym( void *handle, const char *symbol, char *error, int errorsize ); extern int wine_dlclose( void *handle, char *error, int errorsize ); +extern void __wine_dll_register( const IMAGE_NT_HEADERS *header, const char *filename );
Functions starting with '__wine' are internal only and must not be declared in the public headers if it can be avoided.
Selon Alexandre Julliard julliard@winehq.org:
Rémi Assailly remi.assailly@free.fr writes:
--- include/wine/library.h 2005-01-07 19:41:26.000000000 +0100 +++ include/wine/library.h 2005-01-07 19:49:41.389057824 +0100 @@ -42,6 +42,7 @@ extern void *wine_dlopen( const char *filename, int flag, char *error, int
errorsize );
extern void *wine_dlsym( void *handle, const char *symbol, char *error,
int errorsize );
extern int wine_dlclose( void *handle, char *error, int errorsize ); +extern void __wine_dll_register( const IMAGE_NT_HEADERS *header, const
char *filename );
Functions starting with '__wine' are internal only and must not be declared in the public headers if it can be avoided.
-- Alexandre Julliard julliard@winehq.org
Can we create "private" headers ? headers which will be only used in files where some declarations are missing ?
Rémi Assailly remi.assailly@free.fr writes:
Can we create "private" headers ? headers which will be only used in files where some declarations are missing ?
No, at least not in this case. These are used in generated files that must not depend on other headers.
-
Alexandre Julliard -
Rémi Assailly