Retrospective update on memory API
New `flag' class for classifying bitfield bits
Equipped `register' with the EFLAGS register
Equipped the `processor' with the EFLAGS register
Mofied `arch' data structure
Abstraction, now providing concrete Intel registers
Much smaller `processor' class using new registers
Fixed a bug in `memory'

The `mem.get' implementation returned decimalized bytes instead of
hexadecimalized ones; fixed.
Reserved a workbench area for experimentatl code
Precise opcode and instruction set reference

This reference is intended to be precise opcode and instruction
set reference (including x86-64). Its principal aim is exact
definition of instruction parameters and attributes.

The author of this file is Karel Lejska, and the file was copied
from http://ref.x86asm.net/x86reference.xml
Added more utility functions to `arch' as required
New packed() utility for `bitfield' and `register'

packed
Reimplemented memory data structure, added stack

The memory data structure was an array, which made an address like
0xFF000000 extremely silly.

It has now been reimplemented as a hash, which is an improvement.

Also implemented a stack object which "mmaps" onto the memory object.
Merge branch 'feature/stack' into develop
Cleaned up `bitfield' and `register'

The +- functions did not align with the /* functions, they now do.
That means they can handle more than just integers, such as register
or bitfield objects as appropriate.
Norman's unit testing code back in action

The broken tests are not enabled; they will be enabled as they start
passing.
Stack push and pop basic fixes and unit tests
Merge branch 'feature/stack' into develop
Clean-up of the `architecture' class
Implemented the first CPU instruction; `mov'

Of course required scaffolding code missing was discovered and added,
hence the amendment to so many classes.  If this is deemed as a clean
solution, we can work on implementing the next instruction.

The design is likely to change as the first instructions are added,
but will expectedly stabilize after it has been fiven enough
development time to mature.