Torsten Ruger d396da16e3 start with #14 by implementing factory
page was maybe a too low level name
pages may be the unit of the syscall, but after that objects desolve (maybe later to be added on from different pages)
Factory has the job of handing out a new instance of a type
it keeps a freelist for that and a reserve
2018-08-23 19:55:06 +03:00
..
2018-07-27 10:46:22 +03:00
2018-04-19 10:00:55 +03:00
2018-07-03 10:12:40 +03:00
2018-05-20 14:45:48 +03:00
2018-08-18 20:06:15 +03:00
2018-08-19 17:29:04 +03:00
2018-07-25 11:06:42 +03:00
2018-06-16 21:01:15 +03:00
2018-08-06 13:07:06 +03:00
2018-07-07 17:34:08 +03:00
2018-08-06 13:07:06 +03:00

Testing

Tdd, Bdd , Xdd, whatever you call it, i have come to the point where it is a way not only to write software, but to think about software. Ie:

  • if it's not tested, we don't know it works
  • test first makes me think about the software from the outside. (good perspective)

I used minitest as the framework, just because it is lighter and thus when the time comes to move to rubyx, less work.

All

'''' ruby test/test_all.rb ''''

Parfait, Risc , Arm , Mom

Follow the directory structure of the source and may be called unit tests

Risc/Interpreter

Contains many system tests that rely on everything else working. Should be hoisted i guess.

Main

Much like the Interpreter test, but for Arm. This is where the currently few executables are generated and there is an automatic way of running them remotely.

The plan is to integrate this with the interpreter directory