Skip to content
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

Split into multiple pages, one per architecture #14

Open
fghsgh opened this issue Sep 2, 2024 · 1 comment
Open

Split into multiple pages, one per architecture #14

fghsgh opened this issue Sep 2, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@fghsgh
Copy link

fghsgh commented Sep 2, 2024

I propose splitting the Z80 and Z180 tables into two separate pages.

My main reason for this is that adding the Z180 instructions in the recent(ish) update took over the space that was previously occupied by several undocumented opcodes (namely the NEG, RETN and IM duplicates), which hinders work on real hardware as well as emulator development.

It would also provide an infrastructural solution to #1 and #2.

@deeptoaster
Copy link
Owner

That's a good point. I suppose we could have a URL structure that's something like

  • /table/, /table/opcode-table.json: Z80
  • /table/z180/, /table/z180/opcode-table.json: Z180
  • /table/8085/, /table/8085/opcode-table.json: i8085

...and so on. Just need to actually scrape some manuals at some point...

@deeptoaster deeptoaster added the enhancement New feature or request label Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants