summaryrefslogtreecommitdiff
path: root/doc/UsersGuide/UtilityRoutines.tex
diff options
context:
space:
mode:
authorjthorn <jthorn@17b73243-c579-4c4c-a9d2-2d5706c11dac>2002-08-12 16:31:06 +0000
committerjthorn <jthorn@17b73243-c579-4c4c-a9d2-2d5706c11dac>2002-08-12 16:31:06 +0000
commit1dabf7d3156e49c6ea9eb0b1f5d987648042f379 (patch)
tree8482a86b46f941c4c189ed4502d0d0e02789f6c1 /doc/UsersGuide/UtilityRoutines.tex
parentc7c7fa89f712847b7fb86bd30fb61dddaf5ba396 (diff)
FunctionReference.tex (description of Util_TableCreate())
add a detailed description of possible flags and what they mean (at present there's just one, to specify whether keys should be compared as case-sensitive or case-insensitive strings) UtilityRoutines.tex remove detailed description of table flags, text now just points to detailed description of Util_TableCreate() in appendix E2 (= FunctionReference.tex) this checkin closes (or at least _should_ close) problem report documentation/1132 git-svn-id: http://svn.cactuscode.org/flesh/trunk@2946 17b73243-c579-4c4c-a9d2-2d5706c11dac
Diffstat (limited to 'doc/UsersGuide/UtilityRoutines.tex')
-rw-r--r--doc/UsersGuide/UtilityRoutines.tex40
1 files changed, 8 insertions, 32 deletions
diff --git a/doc/UsersGuide/UtilityRoutines.tex b/doc/UsersGuide/UtilityRoutines.tex
index 215a5793..0b9868d5 100644
--- a/doc/UsersGuide/UtilityRoutines.tex
+++ b/doc/UsersGuide/UtilityRoutines.tex
@@ -93,6 +93,14 @@ set entries in it based on a parameter-file--style string.
As well, there are ``table iterator'' functions \verb|Util_TableIt*()|
to allow manipulation of a table even if you don't know its keys.
+A table has an integer ``flags word'' which may be used to specify
+various options, via bit flags defined in \verb|"util_Table.h"|.
+For example, the flags word can be used to control whether keys
+should be compared as case-sensitive or case-insensitive strings.
+See the detailed function description of \verb|Util_TableCreate()|
+in section~\ref{sect-FunctionReference/UtilityFunctions} for a list
+of the possible bit flags and their semantics.
+
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{A Simple Example}
@@ -312,38 +320,6 @@ of the same type (either all integer or all real).
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\section{Table Options}
-
-A table has an integer ``flags word'' which may be used to specify
-various options, via bit flags defined in \verb|"util_Table.h"|.
-At present there is only a single option:
-\begin{description}
-\item[Keys May be Case-Sensitive or Case-Insensitive:]
- By default keys are treated as C-style character strings,
- and the table functions compare them with the standard C
- \verb|strcmp()| function.
- However, by setting the \verb|UTIL_TABLE_FLAGS_CASE_INSENSITIVE|
- bit in the flags word, this table's keys may be made
- case-insensitive, \ie{} the table routines then compare
- this table's keys with \verb|Util_StrCmpi()|.%%%
-\footnote{%%%
- It's not entirely clear how non-ASCII characters
- like \c{c}, \'{e}, \ss, \dots should be handled in
- this case (some of them have only a single case).
- And what about the 16-bit Asian character sets
- used for Chinese, Japanese, Korean, \dots.
- In general, Cactus basically just ignores
- internationalization issues. Sigh\dots
- }%%%
-{}
- Note that keys are still {\em stored\/} exactly as
- the caller specifies them (\ie{} they are {\em not\/}
- forced into a canonical case); it's only their
- {\em comparison\/} that's affected by this flag.
-\end{description}
-
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
\section{Table Iterators}
\label{sect-UtilityRoutines/tables/table-iterators}