shazz

I wake up this issue as it would be a great improvement as complex application requiring detailed and fine memory organization is hard to design without segments.

I like the fact you can split a segment and continue to append code to it :D Even if I have no clue what could be the usage. In terms...

> > ```assembly > !segment code(start=$810, end=$820) > !segment data(start=$830, end=$840) > ``` As the `end` looks mandatory (I was wondering if it makes sense of not. Not totally sure...

#### About !binary I really prefer the keyword syntax, I always thought you kept the `!binary "file2.bin",256,8` syntax to look like old cross-assemblers. I don't really like it, I never...

I think is first idea is fine, `!segment (...)` to define, `segment ` to use. Less confusion.

Question raised under the shower this morning. Segments are also useful to split huge codebase (particularly unmanageable in assembly) into small chunks. Will it be possible to include the segments...

If the segments are split in multiple files, how the cli will look like ? Something like that? ```` c64jasm --disasm-file hello_world.lst --labels-file hello_world.labels --out hello_world.prg START.asm CHARSET.asm ````

I agree with @neochrome. **In details**: - limit on start parameter makes sense to me. I don't have in mind a case when segment start address may be defined after...

Btw, building the branch generates some warning: ```` added 367 packages, and audited 434 packages in 6s 14 vulnerabilities (12 low, 2 high) ```` Is it.. important ?

for outputs I meant, the assembling process will: - output every segment binary in separate file (possibly a PRG to get the start address in the header) if requested (--out,...