In a bit similar vein, another thing that came up recently was the desire to implement segment modifiers as functions inside the scripting language instead of having to make a Java plugin. This would make it easy to spit out assembled structures in particular custom formats without having to implement and/or invoke external tools (e.g. cartconv).

.segmentmodifier AddMoveData() {
    .var blocks = segment.getMemoryBlocks()
    .foreach (block in blocks) {
        .fill block.bytes
        .word block.bytes.size()-1
        .word block.start+block.bytes.size()-1
    }
    .byte blocks.size()	
}

This looks good to me as is! I don't think there's need for anything more specific, since getting access to the raw data provides all the flexibility one needs.

Is block.bytes the same type of object you get from e.g. LoadBinary? Also, what's that single-argument .fill directive? I don't think I've seen that kind of usage mentioned anywhere. Is that .foreach a new general looping construct?

Slammer: One thing i miss in my two go-to assemblers 64tass and ca65, and which i haven't seen in any other 6502 assembler so far, is... *drumrolls*

a .float directive emitting BASIC 5-byte floats.

Like this

baseline:   .float .39 ; kBps KERNAL LOAD throughput (1x speed)

would be equivalent to

baseline:   .byte $7f,$47,$de,$23,$10

but a lot more convenient for the user. I reckon this would not be terribly hard to add? =) (Planning to pester Soci about this.)

What do you need it for? (Usecases?)

Quoting Slammer

What do you need it for? (Usecases?)

Working with the ROM float routines, ofc.

Came in handy with data throughput calculation with Transwarp, some precalc stuff in Artefacts, and lately, on 80-column PET, calculating FPS from cyclecount between VSYNC signals, e.g.

#2: Did I hear version?? In that case would it be possible to allow one or two additional passes to resolve labels (if that indeed would fix the issue)?

No-sense Example:

    .if (TestLabel == $1000) {
        lda #$00
        sta $d020
    } else {
        lda #$00
        sta $d020
        sta $d021
    }

TestLabel:

This would for example allow pseudocommands automatically select long branches (forwards) for example or make "optimizations" where an immediate value passed to a mov16 command which has the same hi and lo byte be optimized (and there were other usecases as well but can't remeber of the top of my head).

Ok, What I was trying to figure out is if it was a one time occurance.

Giving it a .float directive feels wrong (Like mixes two worlds) but I guess thats a matter of taste.

If someone needed it in Kick Assembler I think I would make a getExponentBits(d) and getMantissaBits(d) and then it would be possible to make a macro that produced any float format you like.