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

URL: http://pumpkindb.org/doc/master

Upon initial load, all documentation pages are scrolled down just a tiny bit, but it makes a bad initial impression (feels messy). Has something to do with the gitbook theme we're using, I suppose. When pages are changed by clicking on menu items, there is no such issue because subsequent navigation is done over AJAX.

![screenshot 2017-04-22 15 2

We need to be able to generate docs from the docs key in about blocks, particularly to produce docs for the common vocab on the website. I’m guessing we’ll go with Markdown for formatting, but I’m open to other ideas.

I'm trying to code up an spi-read function. I guess it needs to be implemented using the spi-send function but there is no documentation on how the function works. Also I would like to know how to set the spi speed correctly for the spi-init function.

If you can either provide me with an spi-read function or point me at some documentation so I can code one myself I would appreciate it.

See discussion in #233

This could be added to the manual, and/or example source code on disk.

Thinks I will probably add in the near future:

• provide demo apps for some common embedded platforms like AVR atmega8, LPC1334, etc
• provide primitives for accessing fixed sized words in the dictionary
• write some documentation about things in which zForth differs from 'regular' forth, mostly considering the variable cell size in the dictionary

Started a new Forth kernel project targeted for the Arduino. This time a more traditional multi-tasking token thread kernel with the focus on performance, foot-print and integration with Arduino core functions and libraries.

Written in C++ with approx. 110 kernel functions. Kernel foot-print is 3.5Kbyte without dictionary strings. The dictionary strings adds 750 bytes. A built-in trace adds ap

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