I'd like to create pointer tables where the low bytes and high bytes are separated out like this example from the wiki:
Code: Select all
PointerTableL
.db <Pointer1, <Pointer2
PointerTableH
.db >Pointer1, >Pointer2
Moderator: Moderators
Code: Select all
PointerTableL
.db <Pointer1, <Pointer2
PointerTableH
.db >Pointer1, >Pointer2
True, but it can be mitigated by "bank chaining", where you declare the chained 8K banks ahead of time with the same name, and it will automatically go to the next 8K bank if it is already defined with the same name as the current bank.Pokun wrote:Ah yes this one right? Lots of new features! But you never removed the 8k banks did you? That is what I think most people dislike the most about Magickit/PCEas/NESASM.
It doesn't seem difficult to me, since using < for zero page already implies the low 8-bits (although perhaps sometimes it can make it more difficult to detect errors).I'm pretty sure Elmer's fork of PCEas still uses < for zero page addressing while using <, > and ^ aliases for the mentioned functions. I don't know if he had to do something special to make sure it doesn't conflict.
Yes, it is one of the things I like about it too.Actullay the use of < for zero page addressing is one thing I like about Magickit/PCEas/NESASM. It makes it clear that you are using zero page addressing (if I remember to use it that is), and it makes it possible to choose which addressing mode you want (if you need it for timing or whatever).