[Octave-bug-tracker] [bug #57205] meaningless error reports for F9

[Lars Kindermann]

Follow-up Comment #9, bug #57205 (project octave):

After playing around with errors I would strongly opt for dropping line
numbers from all error mesages ocurring in direct command line input, eiher
typed, pasted or executed by F9. In my opinion they are useless for
interactive work. Mostly they show line '1 column 1' only and are even
misleading in other cases.
See bug #57239 "errors in multiline constructs"    

For F9 it might be helpful to cite the line verbatim which caused the error,
something like 
error: 'xyz' undefined in command 'x = xyz + 1'  

To demonstrate current behaviour, copy this script to the editor


1
if 2
 3
 x4
 5
end
7paste
  

and run it (F5)


>> aaa

ans = 1
ans = 3
error: 'x4' undefined near line 4, column 4
error: called from
    aaa at line 4 column 2
>>


mark it and execut it (F9)


>> 1
ans = 1
>> if 2
>>  3
ans = 3
>>  x4
error: 'x4' undefined near line 1, column 1
>>


and copy/paste it into the command window


>> 1
ans = 1
>> if 2

 3

 x4

 5

end
ans = 3
error: 'x4' undefined near line 9, column 9
>> 7
ans = 7
>>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57205>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/