Hi Witek
good to know you're developing with Rivet. I recommend the reading of
the manual pages
http://tcl.apache.org/rivet/manual3.1/catch.html
http://tcl.apache.org/rivet/manual3.1/try.html
which explain the whole business about these shadow commands
regards
-- Massimo
On 2/12/19 2:54 P
> 2) AbortScript interrupts the execution by returning a special and
> reserved error code that signals the call to abort_script. In order
> prevent a 'catch' or 'try' construct from trapping this error two
> shadow commands were introduced: ::rivet::try ::rivet::catch.
Hello,
Thanks for exp
I'm testing your problem with Rivet 2.3.5/2.4.0 but think the same
discussion could apply to 3.0/3.1
There are two issues with your code:
1) abort_page is meant to have effect only once. That means that the
command is supposed to interrupt the request processing and hand the
execution straigh
Hello,
Maybe I`m getting something wrong but shouldn`t "abort_page" stopped
executing code completely? I have a simple example where it does not.
Can anybody explain me why external_problem is set and why then the
external abort_page is not executed? Tested using rivet-2.3.5 and 3.1.1
--
Wit
