About the language
 

Blitz is a language which is case SENSITIVE, meaning that 'FOO' and 'foo' will be treated differently. This goes for everything from variables and user-created functions, to macros (all of which will be explained later).

Commands which are built in to the language (either from the standard or third-party libraries) will be recognised and tokenised (highlighted). Commands are the only item in the language which are not case sensitive. For example, 'mousewait' and 'MOUSEWAIT' would both be recognised as the MouseWait command.

Commands can also come in three flavours: statements, functions or commands (note that these are different from user-defined statements and functions). A statement returns no value, so the parameters are not put in parenthesis (e.g. "A_Statement parameters"). Functions return a value (which can be used in any kind of expression, as long as numeric return values are used in numeric expressions and string return values are used in string expressions) and so the parameters must be enclosed in parenthesis (e.g. "expression A_Function(parameters)" or "foo=A_Function(parameters)", etc). Multiple parameters are separated by commas, and any kind of expression can be used as a parameter, as long as numeric expressions are used for numeric parameters and string expressions are used for string parameters. A command can be used as either a statement or a function. Commands in the example code on these pages are shown as the MouseWait command in the above paragraph.

Comments in the source are marked using a semi-colon ';' character - the compiler will ignore everything on a line after a semi-colon. Comments in the example code on these pages will be shown like this: ; Here is some example code.

You can also use the colon character (':') to separate different commands on a line, instead of putting everything on its own line. For example "Command1 : Command2 : Command3".


Previous: Before we begin Programming contents Next


News | Introduction | Search | List/Forum/IRC Webring | Contact
Installation | Troubleshooting | Programming | Archives | Links
Return to home page
Page last modified: 6th January 2002