From 067fb40ec3ecc89821f559b60eecd451c49fb6a2 Mon Sep 17 00:00:00 2001 From: eschnett Date: Sat, 2 Jul 2011 23:06:23 +0000 Subject: Correct documentation of if statements in schedule Change the documented allowed "if" statements in schedule files from if(CCTK_EQUALS(, )) { ... } to if() { ... } which is what is actually allowed (and commonly used). git-svn-id: http://svn.cactuscode.org/flesh/trunk@4709 17b73243-c579-4c4c-a9d2-2d5706c11dac --- doc/UsersGuide/Appendices.tex | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/UsersGuide/Appendices.tex b/doc/UsersGuide/Appendices.tex index a9995888..f95abc8a 100644 --- a/doc/UsersGuide/Appendices.tex +++ b/doc/UsersGuide/Appendices.tex @@ -1027,12 +1027,14 @@ constructs using the parameter data base. These can be nested, and have the general form: \begin{alltt} -if (CCTK_Equals(<\var{parameter}>,<\var{string}>)) +if (<\var{conditional-expression}>) \{ [<\var{assignments}>] [<\var{schedule blocks}>] \}\end{alltt} +<\var{conditional-expression}> can be any valid C construct evaluating +to a truth value. Such conditionals are evaluated only at program startup, and are used to pick between different static schedule options. For dynamic scheduling, the {\tt SCHEDULE WHILE} construction should be used. -- cgit v1.2.3