From: Vadim Zeitlin Date: Sun, 26 Nov 2006 20:20:52 +0000 (+0000) Subject: replaced some chars with wxChars (patch from Tim Kosse) X-Git-Url: https://git.saurik.com/wxWidgets.git/commitdiff_plain/e215ce5cec83f77a7dc19dd84755b976d91d0ff0?hp=a38cd629d76f1c119383ddc363e48542e3f15061 replaced some chars with wxChars (patch from Tim Kosse) git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@43662 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- diff --git a/docs/latex/wx/arrstrng.tex b/docs/latex/wx/arrstrng.tex index 68cc818143..7fbf58269c 100644 --- a/docs/latex/wx/arrstrng.tex +++ b/docs/latex/wx/arrstrng.tex @@ -12,7 +12,7 @@ uses its knowledge of internals of wxString class to achieve this). This class is used in the same way as other dynamic \helpref{arrays}{wxarray}, except that no {\it WX\_DEFINE\_ARRAY} declaration is needed for it. When a string is added or inserted in the array, a copy of the string is created, so -the original string may be safely deleted (e.g. if it was a {\it char *} +the original string may be safely deleted (e.g. if it was a {\it wxChar *} pointer the memory it was using can be freed immediately after this). In general, there is no need to worry about string memory deallocation when using this class - it will always free the memory it uses itself. @@ -171,7 +171,7 @@ Returns the number of items in the array. \membersection{wxArrayString::Index}\label{wxarraystringindex} -\func{int}{Index}{\param{const char *}{ sz}, \param{bool}{ bCase = true}, \param{bool}{ bFromEnd = false}} +\func{int}{Index}{\param{const wxChar *}{ sz}, \param{bool}{ bCase = true}, \param{bool}{ bFromEnd = false}} Search the element in the array, starting from the beginning if {\it bFromEnd} is false or from end otherwise. If {\it bCase}, comparison is @@ -229,7 +229,7 @@ are done in release mode. \membersection{wxArrayString::Remove}\label{wxarraystringremove} -\func{void}{Remove}{\param{const char *}{ sz}} +\func{void}{Remove}{\param{const wxChar *}{ sz}} Removes the first item matching this value. An assert failure is provoked by an attempt to remove an element which does not exist in debug build. diff --git a/docs/latex/wx/body.tex b/docs/latex/wx/body.tex index 553b6320bd..5e5483f379 100644 --- a/docs/latex/wx/body.tex +++ b/docs/latex/wx/body.tex @@ -592,7 +592,7 @@ it can alert you to problems later on. \subsection{Use wxString in preference to character arrays}\label{usewxstring} -Using wxString can be much safer and more convenient than using char *. +Using wxString can be much safer and more convenient than using wxChar *. Again, I haven't practiced what I'm preaching, but I'm now trying to use wxString wherever possible. You can reduce the possibility of memory leaks substantially, and it is much more convenient to use the overloaded diff --git a/docs/latex/wx/db.tex b/docs/latex/wx/db.tex index e7264d3c24..1e7a688641 100644 --- a/docs/latex/wx/db.tex +++ b/docs/latex/wx/db.tex @@ -1383,7 +1383,7 @@ When called with {\it sqlLogOFF}, the logging file is closed, and any calls to \ \membersection{wxDb::SQLColumnName}\label{wxdbsqlcolumnname} -\func{const wxString}{SQLColumnName}{\param{const char *}{ colName}} +\func{const wxString}{SQLColumnName}{\param{const wxChar *}{ colName}} Returns the column name in a form ready for use in SQL statements. In most cases, the column name is returned verbatim. But some databases @@ -1405,7 +1405,7 @@ before including the column name in a SQL statement} \membersection{wxDb::SQLTableName}\label{wxdbsqltablename} -\func{const wxString}{SQLTableName}{\param{const char *}{ tableName}} +\func{const wxString}{SQLTableName}{\param{const wxChar *}{ tableName}} Returns the table name in a form ready for use in SQL statements. In most cases, the table name is returned verbatim. But some databases