Call a function: Difference between revisions
Content added Content deleted
(Adds slope example) |
|||
| Line 4,143: | Line 4,143: | ||
* Implicit forward calls are supported, as are optional explicit forward declarations, which can occasionally cure compilation error messages. |
* Implicit forward calls are supported, as are optional explicit forward declarations, which can occasionally cure compilation error messages. |
||
=={{header|Phixmonti}}== |
=={{header|Phixmonti}}== |
||
<syntaxhighlight lang="phixmonti"> |
<syntaxhighlight lang="phixmonti">/# Phixmonti does not distinguish between subroutines and functions. |
||
Each word (as they are called), takes its arguments (if any) from the data stack. #/ |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
enddef |
enddef |
||
saludo /# 'saludo' is a user-defined word. #/ |
|||
| ⚫ | |||
2 3 + print /# The '+' sign and 'print' are intrinsic words. The return value is deposited on the data stack #/ </syntaxhighlight> |
|||
getid saludo exec</syntaxhighlight> |
|||
=={{header|PicoLisp}}== |
=={{header|PicoLisp}}== |
||
When calling a funcion in PicoLisp directly (does this mean "in a statement context"?), it is always surrounded by parentheses, with or without arguments, and for any kind of arguments (evaluated or not): |
When calling a funcion in PicoLisp directly (does this mean "in a statement context"?), it is always surrounded by parentheses, with or without arguments, and for any kind of arguments (evaluated or not): |
||