Hamster-Skripte: view about the command language
Program lines
The hamster-script-language is oriented to line. This means that every expression stands in own line and the length of a line of no practical limitation is defeated:
| Permissible: | Print (uppercase (" This is a separate line ")) |
| Does not allow: | Print ( |
| Here uppercase (" This is NO separate line ") | |
| ) |
Very long lines can be broken, while one underlined "_" at the line end the connection aufrechthält. By the execution of the script this mark is replaced with blanks and the following line radical change is removed. So the original line is produced inside again. The following line is allowed thereby again:
| Allows: | Print (_ uppercase (_ |
| " To believe Hardly, but here this is only a line! " _ | |
| ) _ | |
| ) |
Comments
Comments become marks with "*" - begun, the following line text is ignored:
| Allows: | * Psst... A secret about Spammer: |
| Print are quickly rich (uppercase (" ")) * you have no Shift-key! | |
| Does not allow: | Print (_ |
| Uppercase are quickly rich (" ") be not allowed _ * within the area of command of a line! | |
| ) |
However, there is the second sort comments which may be accommodated within a coding line. These "embedded" notes stand within wandered {clips}:
| Permissible: | Print (_ |
| Uppercase (" make money almost ") _ {comment in split line} | |
| ) |