[Top][All Lists]

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

[Octave-bug-tracker] [bug #48665] calling continue in a function outside

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #48665] calling continue in a function outside of a conditional or loop silences stdout, may crash Octave
Date: Fri, 28 Oct 2016 01:06:39 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0

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
--- 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:


  Message sent via/by Savannah

reply via email to

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