I think stdio calls (getC, putC) could need some documentation what userspace can expect from drivers and what not. Of course, it can always happen that a certain device cannot fulfill those expectations, but in that cases you at least know that you may have to update every userspace tool too, and not only make a glue.asm for the kernel.

Examples/Questions:

• What character set is every stdi

In-place relocation is convenient for assembly programmers but a more robust solution would be the traditional relocation tables found in other executable formats like ELF. Adding this would be convenient for C programs as well and would help us simplify the compiler.

1. Add a new KEXC header which points to a relocation table, simply a list of program-relative addresses at which additional pro

The machine the wiki is on:

• Is old and slow
• Costs @suborb money every month
• Only @suborb has access to

Steps to do this:

• Enable wiki on the GitHub project
• Run the migration script
• Upload the wiki
• Fix up any migration errors
• Move examples into examples directory in the main repo
• Provide a redirect script on z88dk.org so google links remain

I realize it would probably take a good deal of work, but it would be nice to have some documentation around the structure of the compiler and its execution flow. I would be interested in contributing to fix the bugs I've reported (big thanks for your prompt responses and fixes), but its difficult to understand the current setup without investing a great deal of energy.

There's almost zero description of how this process is done, which features are available and what results should be expected in various edge-cases.

There's feature of _ working as substitution delimiter documented by macro_test.asm.

Wait until we have lazy-emitting of words!

But this code should work

10 constant x
: f ['] x execute ;

\ f should push 10 to the stack

Likely related to different implementation of mousedown/mouseover/mouseenter.