General Syntax RulesPureBasic has established rules which never change. These are:
ExampleIf a = 10 ; This is a comment to indicate something.
KeywordsAll keywords are used for general things inside PureBasic, like creating arrays (Dim) or lists (NewList), or controlling the program flow (If : Else : EndIf). They are not followed by the brackets '()', which are typically for PureBasic functions.
ExampleIf a = 1 ; If, Else and EndIf are keywords; while 'a = 1' ... ; is a variable used inside an expression. Else ... EndIfKeywords are regularly described in the chapters on the left side of the index page in the reference manual.
FunctionsAll functions must be followed by a ( or else it will not be considered as a function, (even for null parameter functions).
ExampleEventWindow() ; it is a function. EventWindow ; it is a variable.Functions are regularly included in the PureBasic "Command libraries", described on the right side of the index page in the reference manual.
ConstantsAll constants are preceded by #. They can only be declared once in the source and always keep their predefined values. (The compiler replaces all constant names with their corresponding values when compiling the executable.)
Example#Hello = 10 ; it is a constant. Hello = 10 ; it is a variable.
Literal stringsLiteral strings are declared using the " character. Escape sequences are supported using the ~ character before the literal string. The allowed escape sequences are:\a: alarm Chr(7) \b: backspace Chr(8) \f: formfeed Chr(12) \n: newline Chr(10) \r: carriage return Chr(13) \t: horizontal tab Chr(9) \v: vertical tab Chr(11) \": double quote Chr(34) \\: backslash Chr(92)There are two special constants for strings:#Empty$: represents an empty string (exactly the same as "") #Null$ : represents an null string. This can be used for API functions requiring a null pointer to a string, or to really free a string.Warning: On Windows, \t does not work with the graphical functions of the 2DDrawing and VectorDrawing libraries.
Examplea$ = "Hello world" ; standard string b$ = ~"Escape\nMe !" ; string with escape sequences
LabelsAll labels must be followed by a : (colon). Label names may not contain any operators (+,-,...) as well special characters (ß,ä,ö,ü,...). When defined in a procedure, the label will be only available in this procedure.
ModulesModules use a :: (double colon) when referencing a module name. Be careful not to confuse these with single label colons.
ExpressionsAn expression is something which can be evaluated. An expression can mix any variables, constants, or functions, of the same type. When you use numbers in an expression, you can add the Keyword $ sign in front of it to mean a hexadecimal number, or a Keyword % sign to mean a binary number. Without either of those, the number will be treated as decimal. Strings must be enclosed by inverted commas.
Examplea = a + 1 + (12 * 3) a = a + WindowHeight(#Window) + b/2 + #MyConstant If a <> 12 + 2 b + 2 >= c + 3 EndIf a$ = b$ + "this is a string value" + c$ Foo = Foo + $69 / %1001 ; Hexadecimal and binary number usage
Concatenation of commandsAny number of commands can be added to the same line by using the : option.
ExampleIf IsCrazy = 0 : MessageRequester("Info", "Not Crazy") : Else : MessageRequester("Info", "Crazy") : EndIf
Line continuationIf the line contains a big expression, it can be split on several lines. A split line has to end with one of the following operator: plus (+), comma (,), or (|), And, Or, Xor.
ExampleText$ = "Very very very very long text" + #LF$ + "another long text" + #LF$ + " and the end of the long text" MessageRequester("Hello this is a very long title", "And a very long message, so we can use the multiline" + #LF$ + Text$, #PB_MessageRequester_Ok)
Typical words in this manualWords used in this manual:<variable> : a basic variable.
<expression> : an expression as explained above.
<constant> : a numeric constant.
<label> : a program label.
<type> : any type, (standard or structured).
Others- In this guide, all topics are listed in alphabetical order to decrease any search time.
- Return values of commands are always Integer if no other type is specified in the Syntax line of the command description.
- In the PureBasic documentation are used the terms "commands" and "functions" as well - this is one and the same, independently of a return-value. If a value is returned by the command or function, you can read in the related command description.