Implementation ideas

[Polda18]

Here you can share your ideas about how the implementation could be done and how it could be stitched together.

I'll share my two cents first.

Opcodes resolver could use function pointers, the return type would be a function pointer.

Something along the lines of the following:

typedef (*__exec_instr_t)(int, char*);

__exec_instr_t __resolve_opcode_exec(const char opcode) {
    //...
    switch(opcode) {
        case ADC_IM:
            return __exec_adc_im;
        //...
    }
}

Which brings me to another idea. I'm thinking of making it realistic to the actual 6502 CPU. That means the clock speed should be realistic as well, and preferably something that can be adjusted if needed. Each instruction takes various amounts of cycles to execute, which I'm thinking of actually building a max cycles count resolver for each instruction as well.

Something like:

size_t __resolve_opcode_mcyc(const char opcode);

I'll write more ideas as they come to my mind.

[Polda18]

Also, I just remembered that the actual 6502 has many undocumented and unofficial opcodes that may or may not perform various operations. Those opcodes might be good to implement as well, however some of them might be unstable and unsafe to use. I have found a list of unofficial opcodes for NES, but maybe there's a list of them for Commodore 64, which I'm actually using as the model for this emulator.

[Polda18]

I've got another idea. Employ the Claude AI. Create the CLAUDE.md file with /init and fill it with basic premises.