Recent changes to bugs

#10 Semi-colons in quoted text are seen as comments

2018-04-23T19:34:56.177000Z

Thanks for the catch. I'll have a go at it.

Semi-colons in quoted text are seen as comments

2018-04-23T03:52:11.787000Z

Seems that if there is a semi-colon inside of a string or quoted character, it will interpret the semi-colon as the beginning of a comment instead of a character in the string.

mov a, ':'
mov a, ';'

The first line will have no issue, the second line will generate a "missing quote" error message. I believe this error message can come from a few places (dalep, proc_db, proc_dw?) but I believe the source of the issue is the loop at line 1052 in main.c. Not too sure what the best solution is due to my lack of knowledge of the code, but thought it would be of interest to you. Keep up the awesome work on the project!

#9 extra tabs in listing file.

2018-02-16T06:45:22.563000Z

status: open --> closed-fixed

#9 extra tabs in listing file.

2018-02-15T04:16:07.984000Z

I have a fix for this. but the gates are locked.

#9 extra tabs in listing file.

2018-02-14T19:20:20.848000Z

95 0140 C2 3D 01 jnz memset
96 0143 C9 ret
97 01 44 s171463 equ $
98 0144 21 AC 04 lxi h,outfile
99 ;pzzp packfd "TEST.OUT"
100 01 47 pzzp equ $
101 ;

can't really see it with proportional spaceing ....

extra tabs in listing file.

2018-02-14T19:18:59.281000Z

the assembler is adding extra tabs in the list file ... intermitantly... well there is a pattern

extra tabs in listing file.

2018-02-14T19:18:59.281000Z

Ticket 9 has been modified: extra tabs in listing file.
Edited By: Jay Cotton (jacotton)
Status updated: u'open' => u'closed-fixed'

#8 Possible overflow bug in hex generator

2018-01-19T05:14:22.333000Z

I spent some time today looking at the CP/M manual' ASM chapter: https://www.tramm.li/i8080/cpm22-m.pdf. It explicitly states that labels are case insensitive (page 79) and that machine instructions can be used in the operand field (page 82). So what I thought were questionable constructs are actually valid according to that assembler. If your aim is to be as compatible with old sources as possible, maybe it's worth perusing.

#8 Possible overflow bug in hex generator

2018-01-17T02:14:04.458000Z

You're right.. this code is not optimal. I've found a lot of questionable sources on altairclone.com that break your assembler. Another example is HEXLOAD.ASM which is trying to use the "ret" mnemonic to load the opcode for that instruction into H:

        lxi     h,ret           ;H=0, L=RET instruction

I'm not sure if any of these things are really worth accomodating. I'm curious what assembler they're using that lets them get away with this.

And yes, your assembler has been very helpful for experimenting with old sources writen in the Intel syntax. My goal is to write AVR code so that it's to the code running on the Z80 and I can run the original binaries, but it is nice to have a cross assembler to experiment with the sources. The first computer I used at around age 5 was my dad's Heathkit H89 so I've got a lot of nostalgia for the Z80 and for CP/M.

#8 Possible overflow bug in hex generator

2018-01-17T01:48:25.878000Z

Get your code and did a test. Yep. I think we are abusing the hex generator a bit.
I modified your code to (what I think the correct text should be)
;---------------------------------------------------------------
;DISK BUFFER IN RAM RIGHT AFTER THE LOADER
;---------------------------------------------------------------
BUFFER: DW 00H ;FILLS THE EPROM OUT WITH 00'S
org 0

;---------------------------------------------------------------
; AND FINALLY THE STACK, WHICH GROWS DOWNWARD
;---------------------------------------------------------------
STSP: DS 00H ;SPACE FOR STACK
ds 08ch
STACK: EQU $

END

No warnings, and the hex file is nice and short.

BTW: Did my code help you get your project running? Its a cool project...