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

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

[Octave-bug-tracker] [bug #41117] Exception handling difference between


From: Michael C. Grant
Subject: [Octave-bug-tracker] [bug #41117] Exception handling difference between Matlab and Octave (and, a documentation error)
Date: Mon, 06 Jan 2014 03:56:12 +0000
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.73.11 (KHTML, like Gecko) Version/7.0.1 Safari/537.73.11

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

                 Summary: Exception handling difference between Matlab and
Octave (and, a documentation error)
                 Project: GNU Octave
            Submitted by: mcgrant
            Submitted on: Mon 06 Jan 2014 03:56:12 AM GMT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Matlab Compatibility
                  Status: None
             Assigned to: None
         Originator Name: address@hidden
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

In one of the most recent revisions
(http://hg.savannah.gnu.org/hgweb/octave/rev/6fd22474783e), I see this
description of the new exception capability:

"Alternatively, the output of the @code{lasterror} function can be found in a
variable indicated immediately after the @code{catch} keyword, as in the
example below showing how to redirect an error as a warning:"

This is actually not quite correct. In my tests, the "try; catch err; end"
syntax returns a structure in "err" containing two fields: "identifier" and
"message", but *not* "stack".

I would actually *prefer* the stack trace information be included in the
exception information provided by try/catch. And if the goal is MATLAB
compatibility, that this what should be done. But it does not currently seem
to be the case.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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