2018-01-04 00:15:04 +00:00
|
|
|
|
# Function definitions
|
|
|
|
|
|
|
2018-01-18 21:35:25 +00:00
|
|
|
|
Syntax:
|
|
|
|
|
|
|
2018-03-15 22:09:19 +00:00
|
|
|
|
`[segment (<segment>)] [<modifiers>] <return_type> <name> ( <params> ) [@ <address>] { <body> }`
|
2018-01-18 21:35:25 +00:00
|
|
|
|
|
2018-03-15 22:09:19 +00:00
|
|
|
|
`[segment (<segment>)] asm <return_type> <name> ( <params> ) @ <address> extern`
|
|
|
|
|
|
|
|
|
|
|
|
* `<segment>`: segment name; if absent, then defaults to `default_code_segment` as defined for the platform
|
2018-01-18 21:35:25 +00:00
|
|
|
|
|
|
|
|
|
|
* `<modifiers>`: zero or more of the following:
|
|
|
|
|
|
|
2018-03-05 11:05:37 +00:00
|
|
|
|
* `asm` – the function is written in assembly, not in Millfork (obligatory for `extern` functions),
|
2018-01-18 21:35:25 +00:00
|
|
|
|
see [Using assembly within Millfork programs#Assembly functions](./assembly.md#assembly-functions)
|
|
|
|
|
|
|
2018-02-01 21:39:38 +00:00
|
|
|
|
* `macro` – the function is a macro,
|
|
|
|
|
|
see [Macros_and inlining#Macros](../abi/inlining.md#macros)
|
|
|
|
|
|
|
2018-03-05 11:05:37 +00:00
|
|
|
|
* `inline` – the function should preferably be inlined
|
2018-02-01 21:39:38 +00:00
|
|
|
|
see [Macros_and inlining#Inlining](../abi/inlining.md#automatic_inlining.md)
|
2018-01-18 21:35:25 +00:00
|
|
|
|
|
2018-03-05 11:05:37 +00:00
|
|
|
|
* `noinline` – the function should never be inlined
|
|
|
|
|
|
|
|
|
|
|
|
* `interrupt` – the function is a hardware interrupt handler.
|
|
|
|
|
|
You are not allowed to call such functions directly.
|
|
|
|
|
|
The function cannot have parameters and the retrn type should be `void`.
|
|
|
|
|
|
|
|
|
|
|
|
* `kernal_interrupt` – the function is an interrupt handler called from a generic vendor-provider hardware interrupt handler.
|
|
|
|
|
|
The hardware instruction handler is assumed to have preserved the CPU registers,
|
|
|
|
|
|
so this function only has to preserve the zeropage pseudoregisters.
|
|
|
|
|
|
An example is the Commodore 64 interrupt handler that calls the function at an address read from $314/$315.
|
|
|
|
|
|
Unline hardware handlers with `interrupt`, you can treat functions with `kernal_interrupt` like normal functions.
|
2018-01-18 21:35:25 +00:00
|
|
|
|
|
|
|
|
|
|
* `<return_type>` is a valid return type, see [Types](./types.md)
|
|
|
|
|
|
|
|
|
|
|
|
* `<params>` is a comma-separated list of parameters, in form `type name`. Allowed types are the same as for local variables.
|
|
|
|
|
|
|
|
|
|
|
|
* `<address>` is a constant expression that defines where in the memory the function is or will be located.
|
|
|
|
|
|
|
|
|
|
|
|
* `extern` is a keyword than marks functions that are not defined in the current program,
|
|
|
|
|
|
but are likely to be available at certain address in memory.
|
|
|
|
|
|
Such functions should be marked as written in assembly and should have their parameters passed through registers.
|
|
|
|
|
|
|
|
|
|
|
|
* `<body>` is a newline-separated list of either Millfork or assembly statements
|
|
|
|
|
|
|
