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

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

[Octave-bug-tracker] [bug #39441] SQP return variable 'info' conflicts w


From: anonymous
Subject: [Octave-bug-tracker] [bug #39441] SQP return variable 'info' conflicts with info().
Date: Mon, 08 Jul 2013 23:44:58 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36

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

                 Summary: SQP return variable 'info' conflicts with info().
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Mon 08 Jul 2013 11:44:57 PM UTC
                Category: Libraries
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: Charlie Hagedorn
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.6.4
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Severity: Low/Minor

In the documentation (and help page) for sqp, the function prototype is 

[x, obj, info, iter, nf, lambda] = sqp (x0, phi)


Blindly copying that suggestion overloads the octave native function 'info()'


octave:1> info

  Additional information about GNU Octave is available at
  http://www.octave.org

  Links to the mailing list and other resources for getting help with
  Octave are available at
  http://www.octave.org/support.html

  You may also find some information in the Octave Wiki at
  http://wiki.octave.org

  Additional functionality can be enabled by using packages from
  the Octave Forge project, which may be found at
  http://octave.sourceforge.net

  Report bugs to the bug tracker at
  http://bugs.octave.org
  But first, please read the guidelines to writing a helpful report at
  http://www.octave.org/bugs.html
octave:2> info = 2
info =  2
octave:3> info
info =  2
octave:4> 


Would suggest a different naming convention for the function (and any others
like it). It was quite a surprise to see optimization code start spewing
Octave information when I switched to nmsmax where I had previously used sqp.


Is there a warning variable that can be enabled to prevent accidental
overloads?

Thanks!




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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