"Line 0" error when compile (AREV32)
At 28 JAN 2024 08:21:58PM Robert Heard wrote:
Hello all,
Have a tiny program with a couple of FOR loops that build a string of text to be used in a call to MSG().
It seems to compile, but at end (don't blink or you miss it), it reports an error at "Line No." with "0" as the number, and nothing shows under the "Error Message". Not very helpful.
Then I used COMPILEBASIC, and it was more informative, giving the error message:
SYS1224: The procedure cannot be overwritten
I don't understand the error. This was a new record in this BP file.
Any ideas would be helpful.
Thanks,
Robert
At 28 JAN 2024 11:14PM Donald Bakke wrote:
Hello all,
Have a tiny program with a couple of FOR loops that build a string of text to be used in a call to MSG().
It seems to compile, but at end (don't blink or you miss it), it reports an error at "Line No." with "0" as the number, and nothing shows under the "Error Message". Not very helpful.
Then I used COMPILEBASIC, and it was more informative, giving the error message:
SYS1224: The procedure cannot be overwritten
I don't understand the error. This was a new record in this BP file.
Any ideas would be helpful.
Thanks,
Robert
What is the name of your routine?
At 29 JAN 2024 04:25AM Andrew McAuley wrote:
World leaders in all things RevSoft
At 29 JAN 2024 06:03PM Robert Heard wrote:
Name is "TEST.MSG".
I have since copied the 20-odd lines of code to new rec named TEST.MSG2, and all is fine.
It would seem that there is another "$TEST.MSG" somewhere?
Robert.
At 29 JAN 2024 06:06PM Robert Heard wrote:
Thanks for your suggestion Andrew, although I don't really understand the issue.
Have found a resolution by renaming.
When get a chance, will try your suggestion.
Thanks again.
Robert.
At 29 JAN 2024 06:13PM Donald Bakke wrote:
Name is "TEST.MSG".
I have since copied the 20-odd lines of code to new rec named TEST.MSG2, and all is fine.
It would seem that there is another "$TEST.MSG" somewhere?
Robert.
The problem is not that $TEST.MSG already exists. The problem is that TEST.MSG is a reserved routine name, which is what the article Andrew pointed you to was trying to address. I was suspecting the same thing.
I checked the list of reserved names and sure enough, it's on the list:
TestMSG.jpg?rlkey=of79r889az283sun4n2xex4o0&dl=1
So renaming your routine was one solution. You can also modify the reserved list if you want (but buyer beware). Your solution is the safest.
At 29 JAN 2024 07:31PM Robert Heard wrote:
Doh!
Now I see what Andrew was trying to tell me.
Thanks for the clarification.
Robert.