From IFWiki
Revision as of 15:52, 8 July 2013 by Vaporware (Talk | contribs) (Call stack fields)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Call stack fields

The call stack format described here has fewer fields than Quetzal's:

  • No variable number to store result. This isn't required: for frames whose result is not being discarded, the interpreter can look at the byte before the return PC to get the @call opcode's store target.
  • No count of local variables. This is required for some interpreters, but presumably Aimfiz and Fweep always allocate 15 local variables for each routine.
  • No count of arguments passed into the routine. I believe this is required for @check_arg_count to work.

--Vaporware 15:52, 8 July 2013 (UTC)