EDIT: just looked up ca65. It's not the assembler I thought. I don't think this one was around when I was trying to choose an assembler. Looks interesting.
---
I don't understand why people complain about WLA DX so much.
A linker can be _very_ useful. It is very painful to arrange a lot of graphics and data by hand to never cross a bank boundary. Because of the linker step, WLA can do this for you.
Yes, you need to explain the memory map, but it is just a couple lines. And for code that will be relocated to RAM, wla's memory map "slot" feature can be quite useful. I also like the powerful macro features, and .enum to easily "allocate" variables in RAM.
I also like anonymous labels (which other assemblers support as well).
Basically, it has a lot of great features. If you don't like them, you don't have to use them ... with the exception of the linker and the couple lines for the memory map.
In the end, to each their own. But I feel people really misunderstand the power of the linker step.
Let me point out that d4s used WLA for his large coding project, probably for several of the same reasons I like it as well.
Hamtaro126 wrote:
I need a real bunch of help on either converting Nevketsi's SNES Starterkit to CA65 or Converting SMBDIS to WLA-DX
I'm not sure what you need the starter kit for.
When first learning to program for a new system, the most painful step is the time period between when you start coding and the first point you can get the system to give you some feedback ... at that point you can "test" and "play" and "debug" all you want. The starter kit was merely to let people start immediately at that point (and also have a couple reference docs about the CPU and PPU).
As an aside, many people misunderstood and I got complaints that it didn't help people learn how to use the system. But, to me at least, that was not the point ... it was not a tutorial. It was merely a starter kit with example code to let you jump into immediately playing with stuff.
In particular, my "init" routine is total overkill just to force everything to a known state.
Hamtaro126 wrote:
The reason is that I hate the way WLA-DX handles lables and in-code math stuff compared to X816/CA65, When porting, you have to either ruin the code or leave it alone and forget about porting it to SNES!
Out of curiousity, what exactly is WLA DX forcing you to do to the code?
If you prefer x816/CA65, let me know what routines you actually want from my code and I or others here can probably convert it for you. But converting the whole kit would be a pain since I so heavily use wla macro specific stuff in there.