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

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

[Octave-bug-tracker] [bug #54058] break does not stop the script any mor


From: anonymous
Subject: [Octave-bug-tracker] [bug #54058] break does not stop the script any more. Compatibility issue!
Date: Mon, 4 Jun 2018 22:08:48 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0

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

                 Summary: break does not stop the script any more.
Compatibility issue!
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Tue 05 Jun 2018 02:08:46 AM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Hale
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.4.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

In all previous versions "break" was often used for stopping the script safely
without using debug breakpoints. Particularly it was used often for
conditional interruption of program.
Thinking about this, it was the only safe and easy to use termination function
available.

Starting from 4.4.0, break does not interrupt the script any more.
All the older scripts executed incorrectly now.

It is an awful change in compatibility impermissible for minor version number
upgrades!

P.S.
Break is not the same as "return", and older scripts can not always be fixed
by substituting "return" there.

Moreover, CTRL+C has limited functionality now. Unlike in the past, it is not
passed to child processes from the environment, and does not break the binary
modules run from Octave.

So there is virtually no way left for stopping the script safely.




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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