Also, increase STDIO_BUFSIZE to 0x40 so that those while loops work.

Also, always end the CFS chain with a stop block.

fixes #55 #56 #57

ref #80

fixes #80

Also made Makefile actually portable.

By uploading a BASIC loop and then run it, we can reduce the serial
communication to pure content which greatly reduces the overhead and make
the process much much faster.

It's no longer required to use `gmake` under OpenBSD and shell scripts
no longer require bash.

In C this time. Python/Perl code is barely terser than C for these little
tools. Why bother with interpreted?

I know, this is silly, but I'm moving tools to something a bit closer to the
system. I consider perl to be more system-like than python for a simple reason:
perl is part of the OpenBSD base system and python is not.

Also, I'm learning perl and using this as an opportunity.

putc didn't work well with any byte value on most terminal configuration. It
was a bad idea...

This gives the maximum size of the stack at any given moment during the
execution of the program. It's useful to figure out if the stack gets
dangerously close to the heap.

With a 0x4000 RAMSTART, bshell's RAM usage clashed with USER_CODE, making
RAM-using userapp break everything.

Shell replacement sequence beginning in 3, 2, 1...

Also, add the new `bshell` emulated tool. BASIC is on its way to replace the
shell.

fixes #79

Again, same thing as in zasm.

Same thing as in zasm.

It can only print a decimal literal. But still, that's a big step because
I hadn't implemented decimal formatting yet.

That's my mega-commit you've all been waiting for.

The code for the shell share more routines with userspace apps than with kernel
units, because, well, its behavior is that of a userspace app, not a device
driver.

This created a weird situation with libraries and jump tables. Some routine
belonging to the `kernel/` directory felt weird there.

And then comes `apps/basic`, which will likely share even more code with the
shell. I was seeing myself creating huge jump tables to reuse code from the
shell. It didn't feel right.

Moreover, we'll probably want basic-like apps to optionnally replace the shell.

So here I am with this huge change in the project structure. I didn't test all
recipes on hardware yet, I will do later. I might have broken some...

But now, the structure feels better and the line between what belongs to
`kernel` and what belongs to `apps` feels clearer.

Instead of expecting a `USER_CODE` symbol to be set, we expect `.org` to be
set in all userspace glue code. This gives us more flexibility with regards to
how we manage that.

Moreover, instead of making `USER_RAMSTART` mandatory, we make it default to
the end of the binary, which is adequate in a majority of cases.

Will be useful for my upcoming mega-commit... :)

Also important for upcoming mega commit...

Will be important for a mega-commit I'm preparing.

Most of register fiddling routines (which is now the only thing contained
in care.asm) are used by almost all userspace apps, often in inner loops.

That makes the penalty of using jump tables for those a bit too high.
Moreover, it burdens jump tables needlessly.

Because this unit is very small (now that string routines are out), it makes
sense to always include it in binaries.

Can possibly avoid a lot of debugging pain.

Also, make empty strings be parsed as invalid by parseDecimal.

And made them shorter in name. The new ascii.h file allow reuse in userspace
code.

Let's see where it will lead us...

Because scas isn't used as a reference anymore, no need to blacklist its bugs
anymore.