AMOS Compiler issue

[Retro1234]

How long is the code? I think your just have to split it up into smaller parts for testing to determine where the bug is.

[adrazar]

Originally Posted by Retro1234

I think your just have to split it up into smaller parts for testing to determine where the bug is.

I have a suggestion for a concrete procedure! Binary search!

1) Create a brand new file and copy the top half of your original program.
2) For each missing procedure, create a new procedure (empty) at the bottom of the listing to replace the missing one.
3) Do similar for each missing label.
4) At this point the program should contain no errors.
5) Save the file! and try compiling.

If compiling fails, remove the last half from the new program.
If it succeeds, add the next quarter of the original program.
Then repeat from 2). It is a good idea to create a new file for each cycle, so you can easily compare the two last versions.

[Dh73]

don't give up Axel: have faith and you will succeed

[axel_as]

After hundreds more unsuccessful tests, I followed the advice of a fan of mine who more than anything reminded me of a way of proceeding that I had thought of as a last resort: that is, to set up the program using the 'PROCEDURES' rather than the classic 'RETURN...GOSUB', which actually turns out to be excessive and intrusive to the extent that I have abused it, and I had not resorted to the 'procedures' solution before because I didn't want to overturn and/or reset the program from scratch.
In the end I found myself almost forced to do it, but the result of the compilation was a success!

Now I continue to implement other parts of the code, and I believe that it can be published in the first months of 2024, obviously only after the necessary and rigorous tests.
In a few days I went from despair to tranquility...



Thank you Dh73!



See you soon to all of you.