[Octave-bug-tracker] [bug #48665] calling continue in a function outside of a conditional or loop silences stdout, may crash Octave

[Mike Miller]

Update of bug #48665 (project octave):

                  Status:               Confirmed => Patch Submitted        

    _______________________________________________________

Follow-up Comment #6:

This simple change fixes the bug for me. Should we make a similar change for
the "break" keyword as well? Should we report an error when they are not
called within a loop context?


diff --git a/libinterp/parse-tree/pt-eval.cc
b/libinterp/parse-tree/pt-eval.cc
--- a/libinterp/parse-tree/pt-eval.cc
+++ b/libinterp/parse-tree/pt-eval.cc
@@ -115,8 +115,7 @@ namespace octave
     if (debug_mode)
       do_breakpoint (cmd.is_breakpoint (true));
 
-    if (statement_context == function || statement_context == script
-        || in_loop_command)
+    if (in_loop_command)
       tree_continue_command::continuing = 1;
   }
 


    _______________________________________________________

Reply to this item at:

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

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