AuroraMiddleware/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

some broken links fixed

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@10316 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Vadim Zeitlin 2001-05-24 21:35:34 +00:00
parent 44bb263ab2
commit 520d193622
3 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/latex/wx/critsect.tex
View File

@ -1,7 +1,7 @@
\section{\class{wxCriticalSection}}\label{wxcriticalsection} \section{\class{wxCriticalSection}}\label{wxcriticalsection}
A critical section object is used for the same exactly purpose as A critical section object is used for the same exactly purpose as
\helpref{mutexes}{wxMutex}. The only difference is that under Windows platform \helpref{mutexes}{wxmutex}. The only difference is that under Windows platform
critical sections are only visible inside one process, while mutexes may be critical sections are only visible inside one process, while mutexes may be
shared between processes, so using critical sections is slightly more shared between processes, so using critical sections is slightly more
efficient. The terminology is also slightly different: mutex may be locked (or efficient. The terminology is also slightly different: mutex may be locked (or

7
docs/latex/wx/thread.tex
View File

@ -23,9 +23,10 @@ terminate and destroy itself.
This means, of course, that all detached threads {\bf must} be created on the This means, of course, that all detached threads {\bf must} be created on the
heap because the thread will call {\tt delete this;} upon termination. Joinable heap because the thread will call {\tt delete this;} upon termination. Joinable
threads may be created on the stack although more usually they will be created on the heap. threads may be created on the stack although more usually they will be created
Don't create global thread objects because they allocate memory in their constructor, on the heap as well. Don't create global thread objects because they allocate
which will cause problems for the memory checking system. memory in their constructor, which will cause problems for the memory checking
system.
\wxheading{Derived from} \wxheading{Derived from}

6
docs/latex/wx/tstring.tex
View File

@ -138,9 +138,9 @@ string with a NULL) and are in general not very safe (passing NULL to them will
probably lead to program crash). Moreover, some very useful functions are not probably lead to program crash). Moreover, some very useful functions are not
standard at all. This is why in addition to all wxString functions, there are standard at all. This is why in addition to all wxString functions, there are
also a few global string functions which try to correct these problems: also a few global string functions which try to correct these problems:
\helpref{IsEmpty()}{IsEmpty} verifies whether the string is empty (returning \helpref{wxIsEmpty()}{wxisempty} verifies whether the string is empty (returning
TRUE for NULL pointers), \helpref{Strlen()}{Strlen} also handles NULLs correctly TRUE for NULL pointers), \helpref{wxStrlen()}{wxstrlen} also handles NULLs correctly
and returns 0 for them and \helpref{Stricmp()}{Stricmp} is just a and returns 0 for them and \helpref{wxStricmp()}{wxstricmp} is just a
platform-independent version of case-insensitive string comparison function platform-independent version of case-insensitive string comparison function
known either as stricmp() or strcasecmp() on different platforms. known either as stricmp() or strcasecmp() on different platforms.