Conditional coding in Fscript - undocumented options

Question

Looking at some of the fusion installation scripts, I found some
undocumented features in Fscript that I have long wanted.
Some conditional processing at last, even if primitive.
Here they are:
1. Conditional processing
if <argument1> <operation> <argument2>
<fscript command>
endif
or
if <argument1> <operation> <argument2>
<fscript command>
else
<fscript command>
endif
The if-part that is not executed because the condition is not met is echoed
to the output device with "SKIPPED: " comments.
If ...else...endif constructions can be nested. The use of "exit" exists
Fscript, not the innermost condition.
The elements of these commands are:
(1)
<argument1> can be any string, including environment variables such as
%{forte_root}.
<operation> is either "=" (equal) or "!=" (not equal)
In this case <argument2> must be a string (or environment variable)
(2)
<argument1> can be any string, including environment variables
<operation> is "is"
<argument2> is either:
"set" - the <argument1> string is an environment variable with a
value
"unset" - the <argument1> string is not an environment variable
"file" - the <argument1> string points to an existing file
"directory" - the <argument1> string is a directory file
Note that if <argument1> is specified as %{variable}, the <argument> has the
value of the environment variable.
Suppose environment variable myVar is set to "myValue". Then:
if myVar is set <--- this environment variable exists
echo "This is true"
endif
if %{myVar} is set <--- this becomes if myValue is set and
there is no environment variable myValue
else
echo "This is false since myValue is not an environment variable but a
the value of such variable"
endif
2. Set environment variables
setenv <variablename> <stringvalue>
Sets an environment variable to the specified value
3. Output to logfiles
echo <string>
echo <string> >> <filespec>
Outputs the <string> text string to the standard output or redirects it to
the specified filespec. The ">>" is the redirection operator
4. Silence output
Commands that must be executed and must not be echoed are preceded by a "
character. This includes the if / else / endif constructions:
if FORTE_ROOT = "
echo "No Forte root defined"
setenv FAILED Yes
endif
5. Searching for a string in a file
You can inspect a file for a particular string using the SearchFile command.
This sets the environment variable STATUS to either 0 (success) or non-zero
(not found)
SearchFile <filespec> <searchstring>
SearchFile %{FORTE_ROOT}
if %{STATUS} = 0
echo "Found it"
else
echo "No such string"
endif
Some examples:
# Check if FORTE_ROOT is defined as environment variable
If FORTE_ROOT is unset
Echo "Error: FORTE_ROOT is not set"
Exit
EndIf
# Check if FORTE_ROOT is pointing to a directory
If %{FORTE_ROOT} is directory
else
echo "Not a valid directory"
exit
endif
# check if a repository exists before overwriting it by accident
if %{FORTE_ROOT}/repos/myrep.btx is file
echo "Repository file myrep already exists"
exit
endif
# See if the environment variable myrepos is set
if myrepos is set
echo "You defined environment variable myrepos = %{myrepos}"
else
echo "You did not define environment variable myrepos. Now being set to
MYOWN"
setenv myrepos MYOWN
endif
# Start logging in my own logfile
Echo "--------------------------------" >>%{FORTE_ROOT}/log/mylogfile.log
Echo %{$DATE$} >>%{FORTE_ROOT}/log/mylogfile.log
Echo "Begin Load Distribution of my application "
%{FORTE_ROOT}/log/mylogfile.log#Confirm that this is the correct version of Forte.
SearchFile %{FORTE_ROOT}/install/scripts/FORTE.VER "DEV3.0.L"
If %{STATUS} != 0
Echo "Error: Forte version is incompatible for current application."
Exit
EndIf
Theo de Klerk
Architecture & Application Integration
Professional Services
Compaq Computer Corp. - the Netherlands

Answer 1

I found the answer:
The variable declarations were not on the same frame as the if/then statements. I solved the problem by adding (for each variable):
var mywordGrumpy:vocabulary_Grumpy = new vocabulary_Grumpy();
var mywordIncline:vocabulary_incline = new vocabulary_incline();
var mywordOodles:vocabulary_oodles  = new vocabulary_oodles();
This solved the problem! At the time the variables were being called they had not been declared, thus they had no value, thus the error message.