Hi All,
I'm experiencing a strange behiver in the following flow:
code compiles ok and run ok: C:000000H C:000000H C:00FFFFH 000935H CODE I:000000H I:000000H I:0000FFH 000018H IDATA I:000000H I:000000H I:00007FH 000048H DATA C:000000H C:000000H C:00FFFFH 0002C0H CONST X:000000H X:000000H X:00FFFFH 000024H XDATA
Program Size: data=96.0 xdata=36 const=704 code=2357 LX51 RUN COMPLETE. 4 WARNING(S), 0 ERROR(S)
but adding only another char without even code (DATA incress to 49) results with stack problem that RET is jumping to unused address and programs fails.
C:000000H C:000000H C:00FFFFH 000935H CODE I:000000H I:000000H I:0000FFH 000018H IDATA I:000000H I:000000H I:00007FH 000049H DATA C:000000H C:000000H C:00FFFFH 0002C0H CONST X:000000H X:000000H X:00FFFFH 000024H XDATA
Program Size: data=97.0 xdata=36 const=704 code=2357 LX51 RUN COMPLETE. 4 WARNING(S), 0 ERROR(S)
Can someone tell me what could be wrong ?
Abuse of old BASIC terminology - REMing lines, as in adding the REM(ark) keyword in front of them to deactivate them.
Since BASIC doesn't have the same huge market share anymore, it's way better to use a more neutral expression like "commenting out" or something similar.
:) Old is relative
Ok then - comment out
Well, old and old. Todays BASIC without line numbers looks very much different from the original BASIC available in home computers with 4kB RAM ;)
But old in the sense that a lot of developers have either forgotten - or never heard about - the use of REM to comment out code lines, because the world have exploded into a huge number of newer programming languages. The old C standard didn't even have a method to comment out a single line - the // one-line comments was a late inherritance from C++.