diff --git a/doc/funcref.sgml b/doc/funcref.sgml index 4540703b1..3f9de4267 100644 --- a/doc/funcref.sgml +++ b/doc/funcref.sgml @@ -160,7 +160,7 @@ function.

- + @@ -170,7 +170,7 @@ function. - + (incomplete) @@ -230,9 +230,9 @@ function.

- + - + (incomplete) @@ -261,12 +261,12 @@ Low-level disk I/O API.

- + - + (incomplete) @@ -307,7 +307,7 @@ Low-level disk I/O API.

- + @@ -315,7 +315,7 @@ Low-level disk I/O API. - + (incomplete) @@ -350,10 +350,10 @@ Low-level disk I/O API.

- + - + (incomplete) @@ -654,12 +654,12 @@ communication.

- + - + (incomplete) @@ -4209,7 +4209,9 @@ the program ends. +, +, + @@ -4223,8 +4225,15 @@ the program ends. / +The original IRQ vector is restored on program termination even without +calling this function. + , +, @@ -4585,15 +4594,21 @@ the value The function is only available as fastcall function, so it may only be used in presence of a prototype. -The stub saves the zero page registers used by the C runtime and switches -to the provided stack area. This means that it is safe to execute C code, -even if C code was interrupted. Be careful however not to call into the C library, -and do not enable stack checks for the handler function or any other function called -from it. +The stub saves the registers and zero page locations used by the C runtime +and switches to the provided stack area. As a consequence, there is some +runtime overhead, but it it is safe to execute C code, even if other C code +was interrupted. Be careful however not to call C library functions, and do not +enable stack checks for the handler function or any other function called from +it. +The interrupt vector is reset on function termination, so it's not +strictly necessary to call / as part +of the cleanup when the program terminates. +, +, +