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

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

[Octave-bug-tracker] [bug #29986] Minor: calling plot with no arguments


From: Jake
Subject: [Octave-bug-tracker] [bug #29986] Minor: calling plot with no arguments results in errors (instead of just usage)
Date: Sat, 29 May 2010 00:41:45 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100401 Ubuntu/9.10 (karmic) Firefox/3.5.9

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

                 Summary: Minor: calling plot with no arguments results in
errors (instead of just usage)
                 Project: GNU Octave
            Submitted by: epy
            Submitted on: Sat 29 May 2010 12:41:44 AM GMT
                Category: Libraries
                Severity: 3 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.2.4
        Operating System: GNU/Linux

    _______________________________________________________

Details:

octave:1> plot
usage: plot (y)
       plot (x, y, ...)
       plot (x, y, fmt, ...)       plot (x, y, property, value, ...)
error:   /usr/local/share/octave/3.2.4/m/plot/__plt__.m at line 116, column
5
error:   /usr/local/share/octave/3.2.4/m/plot/plot.m at line 186, column 5
octave:1> 

I looked at the m files in question and I'm scratching my head because I
don't know why those lines would throw errors.

The line in plot.m is "axes (oldh)", where oldh is set to gca(). 
"axes(gca())" doesn't seem to throw an error.  The line in __plt__.m is
"usage(msg)", where msg is the usage message you see above.

The only thing I noticed right off-hand is that line 114 of __plt__.m "msg =
sprintf ("%s       %s (x, y, fmt, ...)", msg, caller);" is missing the
trailing newline character.  Of course that wouldn't make it throw an error,
but that's why the last usage line is on the same line as previous.

Anyway, I'm sure it'll be super obvious to someone else as to why the errors
are appearing and not just the usage message.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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