.junk bytes with 64tass exported source

[grue74]

Currently bytes marked as .junk in the project doesnt show up marked as junk in the 64tass output.

Could it be possible to add long comment before and after junk block?
Or some other way to mark those bytes in the exported source.

I'm currently working with a project that was most likely written with a machine code monitor instead of an assembler and there's a lot of junk to get rid of when finally working with exported source.

[fadden]

SourceGen guarantees that the generated assembly code exactly matches the original binary, and makes it easy to confirm by providing an assemble-and-compare function. It doesn't have to do this, and could just zero-fill the junk zones instead. This would prevent a simple binary comparison, which might be fine if the messaging is clear. Also, if you discover it wasn't junk after all, the bytes won't be available in the source unless you re-generate it.

Automatically inserting comments is possible, maybe something like "### 37 junk bytes ###" so it's easy to identify and potentially replace with a reserve-space pseudo-op in case you want to clean it up but maintain alignment. Alternatively, add an end-of-line "junk" comment so you can feed the source code into grep -v "junk\$" and do it all in one go instead of hand-editing everything.

Another possibility would be to define an assembler-specific macro that is functionally equivalent to the bulk-storage pseudo-op. I don't know if this is viable on all possible assemblers, but we're already auto-generating macros for specific situations (e.g. big-endian words). This would make it easy to find the junk with no extra text.

Yet another possibility would be to generate a shell script that has the line numbers of all the junk lines and just strips them out. (This approach feels like the long way around.)

[grue74]

I kind of like this "### 37 junk bytes ###" approach, easy to search for "junk" and see the amount. Usually, there's not that much of those that I couldn't edit and remove them manually.
My workflow is to comment them away and see if everything still works and later when tidying thigs up remove them.