Skip to content

Commit

Permalink
[Ikarus] Fix in CALL package article
Browse files Browse the repository at this point in the history
  • Loading branch information
muczc1wek committed Dec 25, 2023
1 parent 7f4a916 commit 79d4a10
Showing 1 changed file with 1 addition and 10 deletions.
11 changes: 1 addition & 10 deletions docs/zengin/scripts/extenders/ikarus/functions/call.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,16 +41,6 @@ func int hero_GetAssessEnemy() {

### Recyclable
The second version produces code that can be used more than once. Instead of the parameters the user specifies the address where the parameters are to be taken from. In addition to executing the code, the user will receive an address that he can use to repeat the call. This is much faster than rebuilding the call from scratch.

```
/* Receives a pointer. In case the pointer is non-zero,
* the code at this position is executed and 0 is returned.
* In case pointer is zero, the current mode is changed
* into recyclable mode, this means that the call functions
* expect instructions to build a recyclable call. This
* mode will continue until CALL_End(). This allows code like this:
```


```dae
func int Npc_GetPercFunc(var C_Npc npc, var int type) {
Expand All @@ -70,6 +60,7 @@ func int Npc_GetPercFunc(var C_Npc npc, var int type) {
return +funcID;
};
```
> Receives a pointer. In case the pointer is non-zero, the code at this position is executed and 0 is returned. In case pointer is zero, the current mode is changed into recyclable mode, this means that the call functions expect instructions to build a recyclable call. This mode will continue until `CALL_End()`. This allows code like this:
## Start and End

Expand Down

0 comments on commit 79d4a10

Please sign in to comment.