FINALLY. That was hell, but my Z80 assembler in Z80 now parses all Z80 opcodes (794!) and unlike other native assemblers it uses a static binary tree to match strings to opcodes so the lookup code is only 179 bytes and the table is 3'733 bytes! #z80#v80#cpm#retroprogramming#retrocomputing
Total size is currently 5K but it's not finished yet and the limit will be 8KB. Once complete I will rewrite it in itself meaning that you'll be able to assemble your #Z80 projects using a native Z80/CPM assembler, even on PC via RunCPM, rather than massive PC-only toolchains. Z80 software that can't be built on real HW is useless!!
@thelastpsion I don’t know when that will be yet as I want to get #v80 finished, but that has a fixed, limited scope so I should be able to finish that off. I’ve learnt a lot in writing v80 but also that writing very concise #Z80 code ultimately bogs me down in implementation details that are not relevant to the overall #pling language design that is more important