[Octave-bug-tracker] [bug #45496] "error: no default value for argument" fails to give function/line number/etc

[Nick Jankowski]

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

                 Summary: "error: no default value for argument" fails to give
function/line number/etc
                 Project: GNU Octave
            Submitted by: nrjank
            Submitted on: Wed 08 Jul 2015 03:03:49 PM GMT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Other
                  Status: None
             Assigned to: None
         Originator Name: Nick Jankowski
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

working on a model with a rather involved script where a I was getting

error: no default value for argument 3

The problem is I had no idea were the error was being generated. Turns out, it
was about 3 levels down. I had to manually step through the scripts/functions
until arriving at the source of the error.  Just to make sure normal errors
report correctly, I deliberately created a multiplication mismatch on the line
before the one causing the default argument error, and sure enough it
reported:


debug> dbstep
error: binary operator '*' not implemented for 'matrix' by 'function handl
e' operations
error: called from
    etafn at line 34 column 9
    Yangmodel_transientprofiles> at line -1 column -1
    Yangmodel_output at line 24 column 32


removing that error, and rerunning the same script, and the only output it
provided was:


debug> dbstep
error: no default value for argument 3


Not sure if there's a reason why the error would be unable to display the full
error trace. if it matters, etafn is a subfunction defined within the script
Yangmodel_transientprofiles, later called from Yangmodel_output.  I'm in the
process of moving the functions out to separate files for ML compatibility,
but hadn't gotten there yet. don't know if that affects anything about the
trace.

I'd rather not post my full messy model. I hadn't messed with default values
before, but I can try to create a simplified case if it seems necessary.






    _______________________________________________________

Reply to this item at:

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

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