"pattern clashes with a previous instruction pattern" error about customasm HOT 4 CLOSED

This one looks like another annoying limitation of the current implementation of tokendefs...
It seems a revamp of that system is highly called for!

Basically, it doesn't allow you to have an instruction with any plaintext tokens that also happen to be valid tokendefs in another instruction, at the same position. So your {dest:REG} instructions will clash with your REG <- REG instructions, and also your {jmp:J} instruction at the end will clash with the plaintext JMP, JP, and CALL instructions at the start.

For now, I think your best bet would be adding some tokens to disambiguate them, like using LD! A, B for example.

from customasm.

what if i make all of them plain text. i mean it would be annoying since then i would need to manually write down all ~200 Instructions but then it couldn't clash anymore, right?

from customasm.

I was able to do a quick fix for this! It's in master and in the web version, but not yet in a release.

It should now allow what you're trying to do, but watch out for the order of definitions: in your case, you should put the REG <- REG instructions before the {dest:REG} ones.

The rule of thumb now actually works as intended: you should generally define instructions with fixed patterns before the ones with parameters.

from customasm.

thanks for that!

greta i could help improve the program.

from customasm.