ReceiveTempSMS
/
Sweden-Number
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fixed typos.

This commit is contained in:
Pascal Cuoq 1999-01-24 09:47:29 +00:00 committed by Alexandre Julliard
parent d72e2deaec
commit a4f829f497
3 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
documentation/internal-dll
View File

@ -1,15 +1,15 @@
This document describes some points you should know when you are going to This document describes some points you should know before implementing
implement the internal counterparts to external DLL's. Only 32 bit DLL's the internal counterparts to external DLL's. Only 32 bit DLL's
are considered. are considered.
1. The LibMain function 1. The LibMain function
----------------------- -----------------------
These are the way to do some initialising when a process or thread is attached This is the way to do some initializing when a process or thread is attached
to the dll. The function name is taken from a *.spec file line: to the dll. The function name is taken from a *.spec file line:
init YourFunctionName init YourFunctionName
the you have to implement the function: then, you have to implement the function:
BOOL32 WINAPI YourLibMain(HINSTANCE32 hinstDLL, BOOL32 WINAPI YourLibMain(HINSTANCE32 hinstDLL,
@ -26,11 +26,11 @@ BOOL32 WINAPI YourLibMain(HINSTANCE32 hinstDLL,
The problem here is, that you can't know if you have to call the function from The problem here is, that you can't know if you have to call the function from
the internal or the external DLL. If you just call the function you will get the internal or the external DLL. If you just call the function you will get
the internal implementation. If the external DLL is loaded the executed program the internal implementation. If the external DLL is loaded the executed program
will use the external and you the internal DLL. will use the external DLL and you the internal one.
When you -as example- fill a iconlist placed in the internal DLL the When you -as an example- fill an iconlist placed in the internal DLL the
application wont get the icons from the external DLL. application won't get the icons from the external DLL.
To go around this you have to call the functions over pointer. To work around this, you should always use a pointer to call such functions:
/* definition of the pointer type*/ /* definition of the pointer type*/
void (CALLBACK* pDLLInitComctl)(); void (CALLBACK* pDLLInitComctl)();

4
documentation/shell32
View File

@ -12,7 +12,7 @@ base functionality is roughly in place. The missing parts are the icon
the file copy status window. the file copy status window.
The basis comes from Marcus Meissner and I <juergen.schmied@metronet.de> The basis comes from Marcus Meissner and I <juergen.schmied@metronet.de>
implemented the classes and filled function stubs. implemented the classes and filled in function stubs.
2. General Information 2. General Information
---------------------- ----------------------
@ -71,7 +71,7 @@ implemented the classes and filled function stubs.
Undocumented: Undocumented:
MS says: the abID of SHITEMID should be treated as binary data and not MS says: the abID of SHITEMID should be treated as binary data and not
be interpreted by applications. Applys to everyone but MS itself. be interpreted by applications. Applies to everyone but MS itself.
Word95 interprets the contents of abID (Filesize/Date) so we have to go Word95 interprets the contents of abID (Filesize/Date) so we have to go
for binary compatibility here. for binary compatibility here.
I expect the file open/close dialog in comctl32 does so also. I expect the file open/close dialog in comctl32 does so also.

4
documentation/wine.man
View File

@ -37,9 +37,9 @@ libc6 (aka glibc2).
.PP .PP
.B X .B X
must be installed. To use Wine's support for multithreaded applications, must be installed. To use Wine's support for multithreaded applications,
your X libraries must be reetrant. If you have libc6 (glibc2), or you your X libraries must be reentrant. If you have libc6 (glibc2), or you
compiled the X libraries yourself, they were probably compiled with the compiled the X libraries yourself, they were probably compiled with the
reetrant option enabled. reentrant option enabled.
.PP .PP
.B libXpm .B libXpm
must be installed. If you're using Red Hat, make sure the following must be installed. If you're using Red Hat, make sure the following