[Octave-bug-tracker] [bug #50235] return code is zero, even if there was an error

[Carnë Draug]

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

                 Summary: return code is zero, even if there was an error
                 Project: GNU Octave
            Submitted by: carandraug
            Submitted on: Mon 06 Feb 2017 03:07:46 AM GMT
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.2.0
        Operating System: GNU/Linux

    _______________________________________________________

Details:

If there is an error in an Octave program, the return code should be non-zero.
 This was the behaviour in previous versions, but seems like this bug creped
in version 4.2:


$ octave-3.8.2 --quiet --eval "error ('foo');" ; echo $?
error: foo
1
$ octave-4.0.1 --quiet --eval "error ('foo');" ; echo $?
error: foo
1
$ /usr/local/bin/octave-4.2.0 --quiet --eval "error ('foo');" ; echo $?
error: foo
error: unhandled execution exception -- eval failed
0





    _______________________________________________________

Reply to this item at:

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

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