-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editor adds number sequence when line contains a 206 (DEFFN) code #4
Comments
Hint: When you add a DEF FN statement to a program, the ZX basic system adds an empty number sequence (#14 plus 5 zeroes) to any parameter in the comma-separated parameter list. See ROM at $1F86. My assumption is that Basinc tries to mimick this behavior but fails to determine if the 206 is indeed a DEFFN or something else. The issue may be caused by FindDEFFN() / ProcessDEFFN() in BASSupport.pas. I still have no clue how to compile the sources. |
I could not be able to replicate the issue here (tested in 1.75, 1.78, 1.79). |
It would be great to be able to submit defects against the latest version. However, the last commit here is from Oct 21 v1.77. Do you update the GitHub project? |
ok, I finally confirm and understand the problem. as you have perfectly pinpoint, both FindDEFFN() / ProcessDEFFN() was to blame. |
v1.794 It looks like it happens again. Line 9422 is 36*256+206 and BasinC happily inserts 6 bytes into the DATA statement. Removing the chars and saving does not work because it gets added again as soon as you reload the program. BAS file: |
The editor adds a number sequence (#14 plus 5 more bytes) in front of a comma whenever the source code contains the number 206. It also happens when the line number itself is made up from a 206 (lowbyte). See the sample below. Saving this sample and reloading it causes the unwanted number sequence(s) to reappear.
The text was updated successfully, but these errors were encountered: