@startuml !unquoted function SALT($x) "{{ salt %invoke_void_func("_"+$x) }}" as $x !endfunction !function _choose() {+ an example choose one option ()one ()two [ok] } !endfunction !function _wait() {+ please wait operation in progress <&clock> [cancel] } !endfunction !function _success() {+ success congratulations! [ok] } !endfunction !function _error() {+ error failed, sorry [ok] } !endfunction (*) finally removed in some long term future). • You should not use !define and !definelong anymore. Use !function and variable definition instead • !include allows now multiple inclusions : you don't have to use

should not use !define and !definelong anymore. Use !function, !procedure or variable defi- nition instead. – !define should be replaced by return !function – !definelong should be replaced by !procedure URL, so you don't need !includeurl • Some features (like %date%) have been replaced by builtin functions (for example %date()) • When calling a legacy !definelong macro with no arguments, you do have String (str) - these must be surrounded by single quote or double quote. Variables created outside function are global, that is you can access them from everywhere (including from func- tions). You can emphasize

should not use !define and !definelong anymore. Use !function, !procedure or variable defi- nition instead. – !define should be replaced by return !function – !definelong should be replaced by !procedure URL, so you don't need !includeurl • Some features (like %date%) have been replaced by builtin functions (for example %date()) • When calling a legacy !definelong macro with no arguments, you do have String (str) - these must be surrounded by single quote or double quote. Variables created outside function are global, that is you can access them from everywhere (including from func- tions). You can emphasize

should not use !define and !definelong anymore. Use !function, !procedure or variable definition instead. – !define should be replaced by return !function – !definelong should be replaced by !procedure. URL, so you don’t need !includeurl • Some features (like %date%) have been replaced by builtin functions (for example %date()) • When calling a legacy !definelong macro with no arguments, you do have single quote or double quote. Variables created outside function are global, that is you can access them from everywhere (including from functions). You can emphasize this by using the optional global keyword

should not use !define and !definelong anymore. Use !function, !procedure or variable definition instead. – !define should be replaced by return !function – !definelong should be replaced by !procedure. URL, so you don’t need !includeurl • Some features (like %date%) have been replaced by builtin functions (for example %date()) • When calling a legacy !definelong macro with no arguments, you do have single quote or double quote. Variables created outside function are global, that is you can access them from everywhere (including from functions). You can emphasize this by using the optional global keyword

should not use !define and !definelong anymore. Use !function, !procedure or variable definition instead. – !define should be replaced by return !function – !definelong should be replaced by !procedure. URL, so you don’t need !includeurl • Some features (like %date%) have been replaced by builtin functions (for example %date()) • When calling a legacy !definelong macro with no arguments, you do have single quote or double quote. Variables created outside function are global, that is you can access them from everywhere (including from functions). You can emphasize this by using the optional global keyword

start a project, a task or a milestone a number of days before or after today, using the builtin functions %now and %date: @startgantt title Today is %date("YYYY-MM-dd") !$now = %now() !$past = %date("YYYY-MM-dd" on Preprocessing-JSON page) Variables created outside function are global, that is you can access them from everywhere (including from functions). You can emphasize this by using the optional global keyword Boolean builtin functions [%false(), %true(), %not()] For convenience, you can use those boolean builtin functions: • %false() • %true() • %not() [See also Builtin functions] 25.3 Conditions

ohne hierbei den Verbindungsstring am Client ändern zu müssen. Aliase befinden sich in der Datei aliases.conf, mit folgendem Aussehen unter Windows: poker = E:\Games\Data\PokerBase.fdb blackjack.fdb = Anstatt des Dateipfades kann der lokale Verbindungsstring auch über einen Datenbankalias, der in aliases. conf definiert ist, angegeben werden. Das Format des Alias hängt nur davon ab, wie dieser in der