TUFLOW Message 0040: Difference between revisions
Content deleted Content added
Created page with '{{TUFLOW_Message |tuflow_message=ERROR 0040 - No "End If" specified for "If Scenario == ",a, |alt_msg=NA |type=ERROR |message_desc=???? |suggestions=???? |discussion_page=* [...' |
No edit summary |
||
| (14 intermediate revisions by 4 users not shown) | |||
Line 1:
{{TUFLOW_Message
|tuflow_message=ERROR 0040 - No
|alt_msg=NA
|type=[[ERROR]]
|message_desc=No <font color="blue"><tt>End If</tt></font> command was found to close of the <font color="blue"><tt>If Scenario </tt></font><font color="red"><tt>== </tt></font> block.
|suggestions=Add the <font color="blue"><tt>End If</tt></font> command where it is missing.
'''Tip:''' When using commands such as <font color="blue"><tt>If Scenario </tt></font><font color="red"><tt>== </tt></font> indent the commands within the block that follows as this makes it much easier to interpret which commands apply to which event definition. For example:
<tt>
<font color="blue">If Scenario </font><font color="red">== </font>1974
:<font color="blue">Read GIS Z Shape </font><font color="red">== </font> mi\2d_zsh_road_remove.mif
<font color="blue">Else If Scenario </font><font color="red">== </font> exg <nowiki>|</nowiki> OpA
:<font color="blue">Read GIS Z Shape </font><font color="red">== </font> mi\2d_zsh_road_exg.mif
<font color="blue">Else If Scenario </font><font color="red">== </font> OpB
:<font color="blue">Read GIS Z Shape </font><font color="red">== </font> mi\2d_zsh_road_OpB.mif
<font color="blue">End If </font>
</tt>
Other examples of commands that benefit from indenting are:
* <font color="blue"><tt>Start 2D Domain </tt></font><font color="red"><tt>== </tt></font>
* <font color="blue"><tt>Define Event </tt></font><font color="red"><tt>== </tt></font>
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]]
}}
| |||