bernardosulzbach / ahmes Goto Github PK

They are not adequate.

Write about why I needed to implement it in Python (write about testability and practicality).

An obligatory GUI is a bizarre idea for a simulator.

It is a fact that we must know.

It should be a Git LFS file, however.

The documentation of the instructions should be better aligned.

I have it sketched down already.

• The memory file
• Python function that stores a random value on the last 128 bytes of a program and twice as much on the last 128 bytes of another program
• Test it at least twice manually (at least once test an overflow)

Such as Neander, Ramses, and Cesar.

The step() method must increment the instruction count IFF the next read instruction is not a NOP

The methods read_byte(address) and set_byte(address, value) should both increment the memory access count. These methods are required for better control of the application.

They are not documented right now.

A good amount of the work has already been done, but it is not complete yet.

For the computer to behave as expected by the original simulator, a jump should always trigger a reading of the jump address from the memory.

This should be ensured by tests and properly documented.

There is no point in having one here, we should document everything and add examples right in the repository.

Self-descriptive.