-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"pattern clashes with a previous instruction pattern" error #13
Comments
This one looks like another annoying limitation of the current implementation of tokendefs... 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 For now, I think your best bet would be adding some tokens to disambiguate them, like using |
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? |
I was able to do a quick fix for this! It's in 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 The rule of thumb now actually works as intended: you should generally define instructions with fixed patterns before the ones with parameters. |
thanks for that! greta i could help improve the program. |
I'm stupid again and cannot see why this error occours.
https://pastebin.com/0zQz353f
it says that with line 131, if i remove that it will say the same thing for the instruction below. and so on. if i remove all "REG <- REG" instructions it throws out that error again for line 205
The text was updated successfully, but these errors were encountered: