Antonio Niño Díaz

I prefer the {} version because they are less ambiguous: "\foo1" vs "{foo}1" (see https://github.com/rednex/rgbds/issues/63 ). In principle it doesn't sound bad. In practice, this is a lot of work....

I'm not sure if this would be possible in all cases. Example: ``` SECTION "A", ROMX[$4000], BANK[1] LABEL_A: SECTION "B", ROMX[$4000], BANK[2] LABEL_B: SECTION "C", ROMX[$4000], BANK[3] LABEL_C: SECTION "D",...

Oh, I didn't know that. That's something that has to be documented, it's good to know it can be done.

I don't think this is a good idea. This looks like a project-specific problem that could (maybe) be fixed by organizing includes better from the start. In any case, the...

The problem is that linkerscripts force an order to the sections, but the source code solution doesn't.

I was thinking mostly about the gap that the alignment may leave between the sections. I'd like to give flexibility to the linker to place them however they fit.

I think that you can pretty much get the same effect with macros. ``` ELEMENT : MACRO \1:: DB \2 DW \3 ENDM ELEMENT element1, 1, 1234 ELEMENT element2, 1,...

I think that comment should be allowed everywhere... Because it's more predictable. If empty lines allow comments, why do other lines prohibit them? It's completely arbitrary, and counter-intuitive.

As it has been metioned on discord, the biggest problem with translating the tools themselves is that this makes "googling for the error" really hard. I remember having my system...

Not to mention that sometimes other languages don't have words to express computer terms, so it ends up being half English anyway.