octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54801] Erros in subfunctions do not create a


From: Lars Kindermann
Subject: [Octave-bug-tracker] [bug #54801] Erros in subfunctions do not create a valid link to the source code in the command window
Date: Sun, 7 Oct 2018 09:47:57 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

URL:
  <https://savannah.gnu.org/bugs/?54801>

                 Summary: Erros in subfunctions do not create a valid link to
the source code in the command window
                 Project: GNU Octave
            Submitted by: larskindermann
            Submitted on: Sun 07 Oct 2018 01:47:55 PM UTC
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

When the interpreter encounters an error within a subfunction foo in file
bar.m


disp 'this will fail:'
 function foo
  xyz 
 end
foo


the result in the command window is


>> bar

this will fail:
error: 'xyz' undefined near line 3 column 4
error: called from
    foo at line 3 column 4
    bar at line 5 column 1


While clicking the line


   bar at line 5 column 1


jumps to the correct location in the editor, clicking


   foo at line 3 column 4


pops up an error message window, titeled "Octace Editor", incorrectly stating
that


foo is a built in, compiled or inline 
function and cannot be edited.


In addition to create the correct link, I suggest to always include the
filename to the error messages, e.g.


error: called from
    foo at line 3 column 4 in file bar.m
    bar at line 5 column 1 in file bar.m 

 
This would make debuging much easier.





    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]