https://issues.apache.org/bugzilla/show_bug.cgi?id=57501
Bug ID: 57501
Summary: abort_page does not stop page execution after a call
to ::rivet::parse
Product: Rivet
Version: unspecified
Hardware: PC
OS: FreeBSD
Status: NEW
Severity: normal
Priority: P2
Component: Rivet Core Commands
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Version 2.2 on FreeBSD.
After calling ::rivet::parse, a call to abort_page does not stop the execution
of the page, if the included rvt calls abort_page. If the included rvt does
*not* call abort_page, the call in the outer rvt functions as expected.
I'm unclear as to what the intended behavior is. Is the intention that the rvt
executed by ::rivet::parse is independent, with an independent lifecycle, or is
it simply meant as a "function call" inside the outer rvt page?
Test case:
test_parse.rvt:
<?
parse test_parse2.rvt
abort_page
puts "Execution continued."
?>
test_parse2.rvt:
<?
puts "Parsed rvt."
abort_page
?>
As a secondary issue, note that in a rivet + Tcl 8.5 installation, this can be
worked around by placing a "return" call after the parse statement. However,
with Tcl 8.6, this results in the following error:
"errorCode 'TCL UNEXPECTED_RESULT_CODE 0', errorInfo 'command returned bad
code: 0 while executing "namespace eval request { puts -nonewline "" ..."
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
