changed wxLog::OnLog(String) to take wxString instead of wxChar* to avoid unnecessary...

[wxWidgets.git] / docs / latex / wx / texpr.tex

diff --git a/docs/latex/wx/texpr.tex b/docs/latex/wx/texpr.tex
index 70a01967b0f76dceab4f517d46f1b0094e6780f6..739d5facf434eb1a63c8f9629fcb6e2485836014 100644 (file)
--- a/docs/latex/wx/texpr.tex
+++ b/docs/latex/wx/texpr.tex
@@ -4,7 +4,7 @@ wxExpr is a C++ class reading and writing a subset of Prolog-like syntax,
 supporting objects attribute/value pairs.
 
 wxExpr can be used to develop programs with readable and
 supporting objects attribute/value pairs.
 
 wxExpr can be used to develop programs with readable and

-robust data files. Within wxWindows itself, it is used to parse
+robust data files. Within wxWidgets itself, it is used to parse

 the {\tt .wxr} dialog resource files.
 
 {\bf History of wxExpr}
 the {\tt .wxr} dialog resource files.
 
 {\bf History of wxExpr}


@@ -140,7 +140,7 @@ way to the current compilation.
 These are the known bugs:
 
 \begin{enumerate}\itemsep=0pt
 These are the known bugs:
 
 \begin{enumerate}\itemsep=0pt

-\item Functors are permissable only in the main clause (object).
+\item Functors are permissible only in the main clause (object).

 Therefore nesting of structures must be done using lists, not predicates
 as in Prolog.
 \item There is a limit to the size of strings read in (about 5000 bytes).
 Therefore nesting of structures must be done using lists, not predicates
 as in Prolog.
 \item There is a limit to the size of strings read in (about 5000 bytes).