Listing requests
Brought to you by:
japheth
Menu
▾
▴
#45 Listing requests
1. Listings always list the predefined macros @CatStr, @Environ, @InStr, @SizeStr, @SubStr even when they aren't actually used. Is this necessary ?
2. Currently up to 9 bytes of opcodes or data are shown, would it be possible to increase this to 10 bytes or would that leave too little space between the opcodes and source code ?
3. Could long data definitions be listed over multiple lines similar to what MASM does ?
> Is this necessary ?
It depends. Necessary for survival or mental health? Probably not. Necessary for a comprehensive listing? Yes, IMO.
2. and 3.: yes, this should be addressed in the future - the current status can be improved.
Note if JWasm is ever updated to list long data definitions over multiple lines then the dup operator will need to be listed in a similar fashion to MASM to avoid potentially listing hundreds of lines.
After looking at listing.c I see that 9 bytes of opcodes or data is the maximum that can be output on a line because space must be left for the include file indicator or macro level. It should be possible to output a second line of opcodes for LSTTYPE_CODE to handle long instructions (up to 15 bytes). As for data (LSTTYPE_DATA), perhaps up to 4 lines of data could be displayed (36 bytes) before stopping. There doesn't seem to be a way to detect the DUP operator as MASM does so there would need to be limit as to how many data lines are displayed to avoid displaying hundreds of lines for something like "db 4096 dup(0)"
Code already exists to display additional lines at the very end of function LstWrite though there is a comment stating that it works in pass one only even though it looks like it should generally work.
No, it won't work if display of generated code bytes need 1 line in pass one, but 2 in pass two, the listing will be messed up.
Last edit: japheth 2013-10-16