avra reports that it adds zero padding to words with single quotes even if a ,0 is added

[CableGuy67]

There seems to be a problem with the .db items with a tick ' in them. In the sense that avra isn't processing the line. I've noticed it with brackettick and tick. Both words do seem to be okay, it's just the reporting about adding a zero padding that seems totally broken. I can't sort out the single quote device in the avra code. The double quote is well defined so I must be missing something.

[CableGuy67]

It looks like there is a conditional check that is trying to find special characters inside tokens.

AmForth/avr8/tools/avra/src/parser.c

Line 330 in a673f04

if ((data[i] == '\'') || (data[i] == '"'))

There is another just like that a little further down when it is specifically checking for double quotes.

AmForth/avr8/tools/avra/src/parser.c

Line 358 in a673f04

while ((data[i] != '"') && !IS_ENDLINE(data[i])) i++;

Perhaps all that is needed (famous last words) is a case TERM_SINGLEQUOTE: since double quotes don't seem to cause the same problem in the .db lines

[CableGuy67]

Just to follow up on this for my own memory.

For Forth words that contain double quotes, for instance abort" abort-string.asm, they look like this in the .asm file.

.dw $0006
.db "abort",'"'

So the problem seems to be that both the double quote and single quote are allowed as string delimiter but it doesn't look for the same delimiter when looking for the end of the string, it still looks for either or not a matching pair.

Everything does go into the .lst file correctly it is just that if the name has an even number of bytes and a single quote as part of the word's name avra will still add a zero byte as padding for word alignment. In that case an apparent extra zero byte should be added to the .db line i.e:

.dw $ff04
.db "not'",0

[CableGuy67]

I really should leave this open. After looking more closely at the .lst file it seems that even with an extra zero added after the word with a tick AND avra adding a zero byte thinking that it had a odd number of bytes for .db there was only one added with or without the zero. So I'll leave those there for when a fix is come upon. Until then those 2 warnings are going to be there. Both avra and avrasm2.exe spit out identically sized and there are only 2 lines in the hex files that are not identical at 172 and 173 for whatever reason.