command to set rom size

[trillllian]

1. org $0fffff : db 0 is ugly (and technically prevents using that last byte as freespace)
2. sel wanted a way to control how much the rom can be autoexpanded by

so something like romsize 512k..2M to set the size to (at least) 512k, and limit autoexpanding to not go past 2M. romsize 512k would be shorthand for 512k..512k. (so i guess here the .. is an inclusive range... which is inconsistent with the for loop syntax... whatever)

should it error if you try to patch it to a rom that's already longer than the upper bound? or should it truncate?

also we don't have a parser for this size notation. simplest would be to just parse size in bytes as math expressions, but these kinds of expressions would look a bit ugly i think (for 2M you'd need either like 2*1024*1024 or 2<<20)

it wouldn't be too hard to just parse integer literals with suffixes, but i'm afraid it might be too inflexible. though i guess you can work around it with !a #= somemath : romsize !a if you do need to use math there

[areaperson]

Between pad/padbyte (fast but needs bankcross check), rep (fast but deprecated), and for loop (slow but intuitive), I decided on doing rom expansion outside Asar. So this would be a nice and simple feature to have.

[trillllian]

what??? why are you using any looping or doing bankcross checks?

org $1fffff : db 0 works just fine (except for the caveat that the freespace finder can't use that one byte)

if you need to fill the new space with something other than 00 bytes, you can use freespacebyte to change it.

edit: i hope this didn't come across as rude, i am just a bit bewildered by that comment

[areaperson]

@trillllian Not rude at all. I've spent maybe 30 minutes in the Asar docs and I guess still do not understand the colon operator, or the org plus : pattern, even though you gave an example here. (I still can't find a clear explanation in the user manual, but am admittedly in over my head here).

Knowing this, I would not have experimented with those three other methods :) Sorry for creating any noise here - keep it up!

[trillllian]

that's just the "single-line operator" (i didn't come up with that name...) https://r9.pm/asar-artifacts/branch/asar_2_beta/docs/formatting.html#single-line-operator

it's entirely equivalent to

org $01ffff
db 0

i should add it to the list of commands in the manual, other than that idk how to make it more clear...

[areaperson]

Ah, then I am misunderstanding that org will perform the expansion on its own if the address/space doesn't exist yet and a single byte is passed with db. I only saw examples using org to push multi-byte code/data to addresses that already existed (at least that's how I was interpreting it).

Thanks for the info.