Auto-changing _ERRORLINE Line?

[SirCrow]

Is this already a thing?  If I use _ERRORLINE in a handler to point to the actual faulty program line, as seen here:

Code: QB64: [Select]

1. 'This is program line #1
2. 'This is program line #2
3. 'This is program line #3
4.  
5. ON ERROR GOTO Error_Handler
6.  
7. FOR Num = 0 TO 11
8.     Array(Num) = Num * 10 '       <---- Line that causes "out of range" error ----
9. NEXT
10.  
11. END
12.  
13. Error_Handler:
14.  
15. IF _ERRORLINE = 8 THEN BEEP
16. PRINT "Error on line"; _ERRORLINE
17. RESUME NEXT

...and then I insert more lines of code, comments, whatever:

Code: QB64: [Select]

1. 'This is program line #1
2. 'This is program line #2
3. 'This is program line #3
4. 'This is program line #4            <---- Inserted line ----
5.  
6. ON ERROR GOTO Error_Handler
7.  
8. FOR Num = 0 TO 11
9.     Array(Num) = Num * 10
10. NEXT
11.  
12. END
13.  
14. Error_Handler:
15.  
16. IF _ERRORLINE = 9 THEN BEEP
17. PRINT "Error on line"; _ERRORLINE
18. RESUME NEXT

...it seems obvious to me that the 8 on the IF _ERRORLINE line should automatically change to a 9.  Yes?  Of course, yes.  If possible, that is.  I wouldn't know;  I'm just a dummy who manages somehow to write some pretty cool games and such, using my pretty-basic knowledge of BASIC.  Thanks for reading.

[luke]

Code: QB64: [Select]

1. IF _ERRORLINE = 9 THEN BEEP

This is the height of foolishness. Never assume something so definite about line numbers, because they will change at some point; and no, the ide is not going to update random constants for you.

Use multiple error handlers and appropriate application of ON ERROR instead.

[TempodiBasic]

Hi

this code may be better

Code: QB64: [Select]

1. 'This is program line #1
2. 'This is program line #2
3. 'This is program line #3
4. 'This is program line #4            <---- Inserted line ----
5.  
6. ON ERROR GOTO Error_Handler
7.  
8. FOR Num = 0 TO 11
9.     Array(Num) = Num * 10
10. NEXT
11.  
12. END
13.  
14. Error_Handler:
15. ' identify the error for type and feedback line of error and code of error
16. IF ERR = 9 THEN PRINT "at line "; _ERRORLINE; " code "; ERR; "Out of range": BEEP: RESUME NEXT
17. IF ERR = 53 THEN PRINT "Error on line"; _ERRORLINE; "code "; ERR; "file not found": RESUME NEXT
18. RESUME NEXT
19.  

[Cobalt]

This is the height of foolishness.

Hahaha!

 I like that, but perhaps writing code that can error in the first place is the "height of foolishness" an thus we are all fools!

But Luke is right, welcome to the realm of "Be A Responsible Programmer!" don't expect somebody(or something) else to do all the work for you.

[SirCrow]

Hahaha!

 I like that, but perhaps writing code that can error in the first place is the "height of foolishness" an thus we are all fools!

But Luke is right, welcome to the realm of "Be A Responsible Programmer!" don't expect somebody(or something) else to do all the work for you.

At least I can say that by the time I consider a program finished (enough), it runs pretty well without even using a handler routine.
For a programmer as sloppy as myself, with very limited skill and poor concentration, this is very impressive indeed. ;-)