Instruction set for processor

[saku-koodari]

I haven't decided how to implement this. Memory have to design before this.

[saku-koodari]

This issue is highly related with #32 and it's sub-tasks:
#36 (Closed)
#37 (Closed)
#38 (Closed)
I might design those things here as well.

[saku-koodari]

Instructions is so big thing that it would be better to split it into namespace.
There you can make class Instruction which could look like

public class Instruction
{
    public string InstructionMnemonic { get; set; }
    public int LengthInBytes { get; set; }
    public int DurationInCycles { get; set; }
    public Flag[] FlagsAffected { get; set; }
}

Then you create array of Instruction, where an instruction object stores a opcode

[saku-koodari]

I don't think we need that complex system, maybe...
After all opcodes are just word that is easier to read than plain binary

[saku-koodari]

actually I still want to use an own class. Then you can save an extra data you might need.

Other thing is that, instead of you use Flags[](yes, I mistype it earlier), it could be type of byte

public byte FlagsAffected { get; set; }

Then you can set it like this for example:

var ins = new Instrction { FlagsAffected = Flags.C | Flags.N };

all flags combined is 0xF0, so its enough smalla for byte

[saku-koodari]

Instruction set is becoming so big, that it's better to write dll for that, maybe.
I'll forgot that for now. It speed is the issue, then i'll split into dll.

[saku-koodari]

https://github.com/saku-kaarakainen/WinBoyEmulator/wiki/3.1.2-Game-Boy-Processor-Instruction-set/

[saku-koodari]

Maybe operand could be an enum?

[saku-koodari]

So, before I'll write rest of instructions, I'll do GUI. I don't want to waste a time writing a full instruction set and later see that I need some redesigning. I'll start #22: GUI, before I continue with this.