Page 2 of 2
Posted: Wed Mar 28, 2007 3:53 pm
by tepples
beneficii wrote:Unfortunately, this is otherwise among the best assemblers, allowing you to choose your emptyfill, allowing so many ways of accessing memory, allowing you to embed multiple source files and do stuff with them. How discouraging.
Well at least you can still get all those features in CA65+LD65 if you don't need anything beyond the 6502 family.
Posted: Wed Mar 28, 2007 5:07 pm
by blargg
Unfortunately, this [wla] is otherwise among the best assemblers [...]
Hahahahahahahaha. Not my experience at all. Ignoring the crappy documentation, constant extra crap you have to add to opcodes/operands, and the awful error messages, I've found numerous bugs in several areas (even the damn preprocessor can corrupt host memory). The source is a mess to try to extend/fix. If you're doing NES development, I highly recommend ca65.
Posted: Thu Mar 29, 2007 9:57 am
by Bregalad
Just an open question : How handy is CA65 for ROM and RAM bankswitching ?
Does it allow to overwrite a portion of code/data with new stuff without giving any error or warning (this is especially usefull for CHR ROMs) ?
Does it allow to have the same label at the same adress in different banks (usefull to mirror data among banks) ?
It's not that those are crucial, but it is this kind of tricky tricks that make me kinda like wla.
Maybe CA65 is better and all, but... so far I've done well with wla-dx.
Anyway, the worse of all is NESasm.
Posted: Thu Mar 29, 2007 4:11 pm
by tepples
Bregalad wrote:Just an open question : How handy is CA65 for ROM and RAM bankswitching ?
Does it allow to overwrite a portion of code/data with new stuff without giving any error or warning (this is especially usefull for CHR ROMs) ?
Does it allow to have the same label at the same adress in different banks (usefull to mirror data among banks) ?
Yes. A linker script can specify separate, overlapping memory areas (e.g. ROM0, ROM1, ROM2) with the same run address.