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

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

[Octave-bug-tracker] [bug #48082] Cannot set breakpoint on files that ha


From: Emma Ainge
Subject: [Octave-bug-tracker] [bug #48082] Cannot set breakpoint on files that have invalid identifiers as names
Date: Wed, 1 Jun 2016 23:29:41 +0000 (UTC)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

URL:
  <http://savannah.gnu.org/bugs/?48082>

                 Summary: Cannot set breakpoint on files that have invalid
identifiers as names
                 Project: GNU Octave
            Submitted by: kusuri
            Submitted on: Wed 01 Jun 2016 11:29:39 PM GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: kusuri
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.2
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

When I try to set a breakpoint using the GUI or dbstop with a script that has
a name starting with a number, Octave outputs the error: error:
add_breakpoint: unable to find the requested function

For example, I created a script named 1_Test.m , detailed below. 



# Name the file 1_Test.m
disp hello
disp goodbye
# Use mouse to select line 1
# Use "Toggle Breakpoint" from menu bar
error: add_breakpoint: unable to find the requested function



Octave is able to execute scripts with invalid identifier names. For example,
I could use "run 1_Test.m" without trouble.

I see that when I create a file through Octave and name it starting with a
number, Octave gives me a friendly warning that I may run into issues. I
normally name my files outside of Octave, so I was stumped on this for awhile.


Could either this be fixed so that dbstop accepts invalid identifier names, or
could the error that Octave displays let the user know that its their naming
convention that they need to look at?

Thank you!





    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48082>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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