Comp Mark II: Simple 4-bit/1 Hz Virtual Computer

In fairness, (1) a lot of the verbosity of the code here is because of the way C++ makes you separate out declarations and definitions, and makes you declare member functions even when they are just overriding virtual member functions in a base class, and in a nicer language equivalent code would be distinctly less painful; and (2) the 8086 emulator is able to be nice and small partly because its author is very, very, very clever. (Note: author of 8086tiny is my boss.)

The code is just normalized to separate each bit of functionality and each class into its own source file, which IMO can hardly be seen as a negative. Yes you could do the same in a lot less lines of code, in a single source file, but that does not necessarily mean the code would be 'better' (easier to read, debug, maintain), just shorter and easier to analyse by quickly scanning it. If someone would ever like to add more advanced features to this simulator, the advantages of the normalisation and separation of concerns will quickly outweigh the 'downside' of having a few more files than absolutely necessary.

It takes too long to compile otherwise, and I didn't want people to give up during compilation... You can run 'make optimize' to use -O1