memory.d: read() function uses a ubyte address parameter, and write functions use ushort.

[s-daveb]

I thought all NES registers were 1-byte wide?
Maybe we need to implement the memory mapper to "shift" the starting index, allowing us to access other parts of memory.

I was thinking we could use an IMemoryMapper interface and implement different games' mappers as we need them.

[s-daveb]

calling @bobomb

[bobomb]

I think 1 byte reads/writes should be acceptable

[s-daveb]

After our talk a few minutes ago, I think it would be a good idea to have a "backend" (private) implementation of read/write that can access any part of the memoryspace, and public versions of that that go through the memory mappers.

If we define IMemoryMapper in memory.cpp, would classes implementing IMemoryMapper have access to Memory's private methods?

We might have to implement each memory mapper in memory.d otherwise.

See #4