collapseos/emul/.gitignore

/shell/shell
/bshell/shell
/zasm/zasm
/zasm/avra
/runbin/runbin
/*/*-bin.h
/*/*.bin
/cfsin/zasm
/cfsin/ed
/cfsin/basic
/cfsin/forth
/cfsin/user.h
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm 2019-05-17 23:33:20 +10:00			`/shell/shell`
basic: add fls command Also, add the new `bshell` emulated tool. BASIC is on its way to replace the shell. 2019-11-25 02:24:15 +11:00			`/bshell/shell`
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm 2019-05-17 23:33:20 +10:00			`/zasm/zasm`
avra: first steps 2019-12-14 09:38:40 +11:00			`/zasm/avra`
Add the concept of unit tests Will be much much easier to tests new core routines without having to re-create their context first. Also, extract parse.asm from core.asm 2019-05-17 23:33:20 +10:00			`/runbin/runbin`
tools/emul: re-organize .h files What used to be `tools/emul/user.h` was in fact specific to zasm, so I moved it there. To avoid name confusion, I renamed what used to be kernel.h and user.h to kernel-bin.h and user-bin.h. 2019-06-03 22:12:44 +10:00			`//-bin.h`
Make the shell a userspace app 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. 2019-11-16 07:37:49 +11:00			`//.bin`
tools/emul: make shell's cfsin always have all apps compiled in it 2019-06-03 22:32:25 +10:00			`/cfsin/zasm`
apps/ed: first steps 2019-07-13 23:57:37 +10:00			`/cfsin/ed`
basic: begin an implementation from sratch Let's see where it will lead us... 2019-11-14 07:28:16 +11:00			`/cfsin/basic`
apps/forth: new (WIP) application 2020-03-08 04:13:15 +11:00			`/cfsin/forth`
tools/emul/shell: copy user.h in its cfsin This way, we can compile apps from within the shell that run on the shell. 2019-06-03 23:25:47 +10:00			`/cfsin/user.h`