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 Function names must start with a $ • Argument names must start with a $ • Void functions can call other void functions Example: @startuml !function msg($source, $destination) $source --> $destination языку PlantUML (1.2019.9) 147 / 172 19.5 Return function 19 PREPROCESSING Variables defined in functions are local. It means that the variable is destroyed when the function ends. 19.5 Return function

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 Boolean builtin functions [%false(), %true(), %not()] For convenience, you can use those boolean builtin functions: • %false() • %true() • %not() [See also Builtin functions] 20.4 Conditions function that you can call: • directly in variable definition or in diagram text • from other return functions • from procedures • Function name should start with a $ • Argument names should start with a

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 Boolean builtin functions [%false(), %true(), %not()] For convenience, you can use those boolean builtin functions: • %false() • %true() • %not() [See also Builtin functions] 20.4 Conditions function that you can call: • directly in variable definition or in diagram text • from other return functions • from procedures • Function name should start with a $ • Argument names should start with a

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 created outside function are global, that is you can access to them from everywhere (including from functions). You can emphasize this by using the optional global keyword when defining a variable. @startuml Function name should start by a $ • Argument names should start by a $ • Void functions can call other void functions Example: @startuml !function msg($source, $destination) $source --> $destination

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 Boolean builtin functions [%false(), %true(), %not()] For convenience, you can use those boolean builtin functions: • %false() • %true() • %not() [See also Builtin functions] 25.4 Conditions function that you can call: • directly in variable definition or in diagram text • from other return functions • from procedures • Function name should start with a $ • Argument names should start with a

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 Boolean builtin functions [%false(), %true(), %not()] For convenience, you can use those boolean builtin functions: • %false() • %true() • %not() [See also Builtin functions] 24.4 Conditions function that you can call: • directly in variable definition or in diagram text • from other return functions • from procedures • Function name should start with a $ • Argument names should start with a

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 Boolean builtin functions [%false(), %true(), %not()] For convenience, you can use those boolean builtin functions: • %false() • %true() • %not() [See also Builtin functions] 25.4 Conditions function that you can call: • directly in variable definition or in diagram text • from other return functions • from procedures • Function name should start with a $ • Argument names should start with a

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" 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 function that you can call: • directly in variable definition or in diagram text • from other return functions • from procedures • Function name should start with a $ • Argument names should start with a

..................................................................................... 664 RDB$FUNCTIONS ............................................................................................... Приложение A: Дополнительные статьи Поле RDB$VALID_BLR В системных таблицах RDB$PROCEDURES, RDB$FUNCTIONS и RDB$TRIGGERS присутствует поле RDB$VALID_BLR. Оно предназначено для сигнализации о возможной 'Function', RDB$FUNCTION_NAME, RDB$VALID_BLR FROM RDB$FUNCTIONS WHERE RDB$FUNCTIONS.RDB$PACKAGE_NAME IS NULL UNION ALL SELECT 'Package', RDB$PACKAGE_NAME

способ поддержать все возможности стандарта и сохранить все расширения ClickHouse! 2021: Window Functions, ANY/ALL, EXISTS, GROUPING SETS... 2022: Correlated Subqueries Отсутствие оптимизаций JOIN 18