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 Lenguaje PlantUML (1.2019.9) 146 / 171 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 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 when defining a variable. @startuml 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

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 them from everywhere (including from functions). You can emphasize this by using the optional global keyword when defining a variable. @startuml 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

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 them from everywhere (including from functions). You can emphasize this by using the optional global keyword when defining a variable. @startuml 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

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" 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 when defining a variable. @startuml 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

the call stack may impact an unrelated function further up. Error Numbers • Some languages have functions return an error number (or some other error value) separately from the successful return value of most _unchecked functions, is unsafe, because it can create UB if the range is incorrect. abs is incorrect for a different reason: it is an external function (FFI). Calling external functions is usually only only a problem when those functions do things with pointers which might violate Rust's memory model, but in general any C function might have undefined behaviour under any arbitrary circumstances. En este

vacío, lo que es contrario a la lógica común. Manejo de NULL en UDF's Las UDF's (User Defined Functions o Funciones Definidas por el Usuario) son funciones no internas en el motor, por tanto definidas