I've hit a snag with my VM.
The idea was to have something like this:
(Each branch is a "has-a" relationship. I need to learn UML)Code:VirtualMachine / \ / \ / \ VMMemory VMCPU
Trouble is, the VMCPU may need to call VMMemory::Write or VMMemory::Read, depending on the instructions it's executing.
I'm thinking the answer is really simple.
Would it be "better" to work VMCPU into VirtualMachine?
Good class architecture is not like a Swiss Army Knife; it should be more like a well balanced throwing knife.
- Mike McShaffry
Make VMCPU a friend of VMMemory?
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
... Oh yeah.
(Thanks).
Good class architecture is not like a Swiss Army Knife; it should be more like a well balanced throwing knife.
- Mike McShaffry
In the case you only need those two member functions, you may only need to declare them friends of VMCPU. Instead of the whole class.
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
