Difference between revisions of "Template:BuiltinAppSyscallMessage"
From WikiPrizm
Jump to navigationJump to search (Created page with "Note that even though most built-in apps do not return, the calling code is kept on stack and one can return to it using a ugly hack, for example through timers, setjmp and lo...") |
|||
| Line 1: | Line 1: | ||
| − | Note that even though most built-in apps do not return, the calling code is kept on stack and one can return to it using a ugly hack, for example through timers, setjmp and longjmp. | + | Note that even though most built-in apps do not return, the calling code is kept on stack and one can return to it using a ugly hack, for example through timers, setjmp and longjmp. The reason why they don't return is that they expect to use [[GetKey#GetKey_as_an_exit_point|GetKey as an exit point]]. |
Revision as of 18:49, 1 August 2014
Note that even though most built-in apps do not return, the calling code is kept on stack and one can return to it using a ugly hack, for example through timers, setjmp and longjmp. The reason why they don't return is that they expect to use GetKey as an exit point.
