Exceptions/Catch an exception thrown in a nested call: Difference between revisions
Exceptions/Catch an exception thrown in a nested call (view source)
Revision as of 14:05, 13 June 2024
, 13 days ago→{{header|langur}}
(Remove Omit tag for Swift.) |
Langurmonkey (talk | contribs) |
||
(53 intermediate revisions by 20 users not shown) | |||
Line 15:
Show/describe what happens when the program is run.
<br><br>
=={{header|11l}}==
{{trans|Python}}
<syntaxhighlight lang="11l">T U0 {}
T U1 {}
F baz(i)
I i == 0
X.throw U0()
E
X.throw U1()
F bar(i)
baz(i)
F foo()
L(i) 0..1
X.try
bar(i)
X.catch U0
print(‘Function foo caught exception U0’)
foo()</syntaxhighlight>
{{out}}
<pre>
Function foo caught exception U0
</pre>
The exact [http://rosettacode.org/wiki/Talk:Exceptions/Catch_an_exception_thrown_in_a_nested_call#11l_swallows_U1.3F behavior] for an uncaught exception is implementation-defined [as in C++].
=={{header|Ada}}==
<
procedure Exceptions_From_Nested_Calls is
Line 47 ⟶ 76:
Foo;
end loop;
end Exceptions_From_Nested_Calls;</
{{out}}
<pre>
Line 59 ⟶ 88:
=={{header|Aime}}==
<
baz(integer i)
{
Line 99 ⟶ 128:
return 0;
}</
{{out}}
<pre>Exception `U0' thrown
Line 108 ⟶ 137:
=={{header|ALGOL 68}}==
{{trans|
{{works with|ALGOL 68|Standard - no extensions to language used}}
Line 120 ⟶ 149:
c.f. [[Exceptions#ALGOL_68|ALGOL 68 Exceptions]] for more details.
<
INT value,
STRUCT(
Line 175 ⟶ 204:
FI;
foo</
{{out}}
<pre>
Line 189 ⟶ 218:
'''par''' clause, then all parallel the threads are terminated and the
program continues in the parent thread. <!-- example needed -->
=={{header|Amazing Hopper}}==
<p>Hopper has a basic "try/catch" handling, and must be handled manually. Only one exception will be raised.</p>
<p>VERSION 1: </p>
<syntaxhighlight lang="c">
#include <jambo.h>
Main
e=0, se=""
Try
Gosub 'Foo'
Catch (e)
Get msg exception, and Move to 'se'
Printnl ("+-MAIN-FOO CALL Error: ",e, " : ", se )
Finish
End
Subrutines
Define ' Foo '
Gosub ' Bar '
Return
Define ' Bar '
Set '0', Gosub ' Biz '
Set '1', Gosub ' Biz '
Return
Define ' Biz, x '
a=0, b=0
If ( x )
Let ' b:=Sqrt(-1) '
Nan( a ) do{ Raise (1000,"\n+----Func BIZ: NaN!") }
Else
#( a=log(-1) + log(-1) )
Nan( a ) do{ Raise (1001,"\n+----Func BIZ: NaN!") }
End If
Printnl ' "a = ", a, " b = ", b '
Return
</syntaxhighlight>
{{out}}
<pre>
+-MAIN-FOO CALL Error: 1001 :
+----Func BIZ: NaN!
</pre>
<p>VERSION 2: </p>
<syntaxhighlight lang="c">
#include <jambo.h>
Main
e=0, se=""
Try
Gosub 'Foo'
Catch (e)
Get msg exception, and Move to 'se'
Printnl ("+-MAIN Error: ",e, " : ", se )
Finish
End
Subrutines
/*
This "Try" is not considered nested, then, it is necessary
to capture the error and raise the error
*/
Define ' Foo '
Try
Gosub ' Bar '
Catch (e)
Get msg exception, and Move to 'se'
Free try // absolutly nessesary in this chase!
Raise (e, Cat ("\n+--FUNC FOO: ", se) )
Finish
Return
Define ' Bar '
Try
Set '0', Gosub ' Biz '
Set '1', Gosub ' Biz '
Catch(e)
Get msg exception, and Move to 'se'
Free try // absolutly nessesary in this chase!
Raise (e, Cat ("\n+---FUNC BAR: ", se) )
Finish
Return
Define ' Biz, x '
a=0, b=0
If ( x )
Let ' b:=Sqrt(-1) '
Nan( a ) do{ Raise (1000,"\n+----Func BIZ: NaN!") }
Else
#( a=log(-1) + log(-1) )
Nan( a ) do{ Raise (1001,"\n+----Func BIZ: NaN!") }
End If
Printnl ' "a = ", a, " b = ", b '
Return
</syntaxhighlight>
{{out}}
<pre>
+-MAIN Error: 1001 :
+--FUNC FOO:
+---FUNC BAR:
+----Func BIZ: NaN!
</pre>
=={{header|APL}}==
{{works with|Dyalog APL}}
<syntaxhighlight lang="apl">:Namespace Traps
⍝ Traps (exceptions) are just numbers
⍝ 500-999 are reserved for the user
U0 U1←900 901
⍝ Catch
∇foo;i
:For i :In ⍳2
:Trap U0
bar i
:Else
⎕←'foo caught U0'
:EndTrap
:EndFor
∇
⍝ Throw
∇bar i
⎕SIGNAL U0 U1[i]
∇
:EndNamespace</syntaxhighlight>
{{out}}
<pre> Traps.foo
foo caught U0
ERROR 901
foo[3] bar i
∧
</pre>
=={{header|AutoHotkey}}==
=== True exceptions ===
Line 195 ⟶ 370:
In [[AutoHotkey_L]], [http://l.autohotkey.net/docs/commands/Try.htm Try], [http://l.autohotkey.net/docs/commands/Catch.htm Catch], and [http://l.autohotkey.net/docs/commands/Throw.htm Throw] are available to handle exceptions.<br/>
When this program is run, the first exception (U0) is raised, and caught by the try-catch section. This causes a Message Box containing the text "An exception was raised: First Exception" to be displayed by the script. The second exception is not caught, generating a runtime error.
<
global U1 := Exception("Second Exception")
Line 218 ⟶ 393:
else if ( calls = 2 )
throw U1
}</
The runtime error:
<pre>Error: Second Exception
Line 240 ⟶ 415:
The global ErrorLevel keeps track of the last error.
Here is one way to keep track of nested errors:
<syntaxhighlight lang="autohotkey">foo()
Return
Line 269 ⟶ 444:
ErrorLevel .= "U0"
Return 1
}</
=={{header|BBC BASIC}}==
{{works with|BBC BASIC for Windows}}
<
U0& = 123
U1& = 124
Line 299 ⟶ 474:
ENDCASE
ENDPROC
</syntaxhighlight>
{{out}} (the second message is output by the default error handler):
<pre>Exception U0 caught in foo
Line 322 ⟶ 497:
U0 and U1 are boring for debugging purposes. Added something to help with that.
<
#include <stdlib.h>
Line 443 ⟶ 618:
</syntaxhighlight>
{{out}}
<pre>Foo entering bar.
Line 455 ⟶ 630:
*** Error: U1 Bartender Error. Bartender kicked customer out of bar Baz.
</pre>
=={{header|C sharp|C#}}==
This example will first catch U0 and print "U0 Caught" to the console when it does. The uncaught U1 exception will then cause the program to terminate and print the type of the exception, location of the error, and the stack.
<
class Exceptions
{
Line 532 ⟶ 665:
foo();
}
}</
{{out}}
Line 544 ⟶ 677:
</pre>
=={{header|C++}}==
First exception will be caught and message will be displayed,
second will be caught by the default exception handler,
which as required by the C++ Standard, will call terminate(),
aborting the task, typically with an error message.
<syntaxhighlight lang="cpp">#include <iostream>
class U0 {};
class U1 {};
void baz(int i)
{
if (!i) throw U0();
else throw U1();
}
void bar(int i) { baz(i); }
void foo()
{
for (int i = 0; i < 2; i++)
{
try {
bar(i);
} catch(U0 e) {
std::cout<< "Exception U0 caught\n";
}
}
}
int main() {
foo();
std::cout<< "Should never get here!\n";
return 0;
}</syntaxhighlight>
Result:
<pre>
Exception U0 caught
This application has requested the Runtime to terminate it in an unusual way.
</pre>
The exact behavior for an uncaught exception is implementation-defined.
=={{header|Clojure}}==
<
(def U1 (ex-info "U1" {}))
Line 562 ⟶ 736:
(defn -main [& args]
(foo))</
{{output}}
Line 582 ⟶ 756:
=={{header|Common Lisp}}==
<
(define-condition user-condition-2 (error) ())
Line 599 ⟶ 773:
(trace foo bar baz)
(foo)</
{{out}} (the numbered lines are output from <code>trace</code>):
<
1: (BAR USER-CONDITION-1)
2: (BAZ USER-CONDITION-1)
foo: Caught: Condition USER-CONDITION-1 was signalled.
1: (BAR USER-CONDITION-2)
2: (BAZ USER-CONDITION-2)</
At this point, the debugger (if any) is invoked
with the unhandled condition of type USER-CONDITION-2.
=={{header|Crystal}}==
<syntaxhighlight lang="ruby">class U0 < Exception
end
class U1 < Exception
end
def foo
2.times do |i|
begin
bar(i)
rescue e : U0
puts "rescued #{e}"
end
end
end
def bar(i : Int32)
baz(i)
end
def baz(i : Int32)
raise U0.new("this is u0") if i == 0
raise U1.new("this is u1") if i == 1
end
foo</syntaxhighlight>
<pre>
rescued this is u0
Unhandled exception: this is u1 (U1)
from exceptions_nested.cr:28:2 in 'baz'
from exceptions_nested.cr:23:2 in 'bar'
from exceptions_nested.cr:15:7 in 'foo'
from exceptions_nested.cr:31:1 in '__crystal_main'
from /usr/local/Cellar/crystal/0.32.1/src/crystal/main.cr:97:5 in 'main_user_code'
from /usr/local/Cellar/crystal/0.32.1/src/crystal/main.cr:86:7 in 'main'
from /usr/local/Cellar/crystal/0.32.1/src/crystal/main.cr:106:3 in 'main'
</pre>
=={{header|D}}==
First exception will be caught and message will be displayed,
second will be caught by default exception handler.
<
this() @safe pure nothrow { super("U0 error message"); }
}
Line 645 ⟶ 860:
void main() {
foo;
}</
{{out}}
<pre>test.U1(at)test.d(8): U1 error message
Line 657 ⟶ 872:
=={{header|Delphi}}==
{{Trans|D}}
<
{$APPTYPE CONSOLE}
Line 699 ⟶ 914:
begin
Foo;
end.</
{{out}}
Line 707 ⟶ 922:
The uncaught exception shows a Windows Error Report dialog.
=={{header|DWScript}}==
{{Trans|D}}
First exception will be caught and message will be displayed, second will be caught by default exception handler.
<
type Exception2 = class (Exception) end;
Line 741 ⟶ 955:
end;
Foo;</
Result:
<pre>Exception1 caught
User defined exception: Error message 2</pre>
=={{header|Dyalect}}==
<syntaxhighlight lang="dyalect">var bazCallCount = 0
func baz() {
bazCallCount += 1
if bazCallCount == 1 {
throw @BazCall1()
} else if bazCallCount == 2 {
throw @BazCall2()
}
}
func bar() {
baz()
}
func foo() {
var calls = 2
while calls > 0 {
try {
bar()
} catch {
@BazCall1() => print("BazzCall1 caught.")
}
calls -= 1
}
}
foo()</syntaxhighlight>
{{out}}
<pre>BazzCall1 caught.
Error D601: BazCall2</pre>
=={{header|EchoLisp}}==
<
(define (foo)
(for ((i 2))
Line 769 ⟶ 1,019:
"U0 raised" catched
👓 error: U1 not catched
</syntaxhighlight>
=={{header|EGL}}==
{{incorrect|EGL|calls to bar() from foo should be equivalent. Second call can't catch anything.}}
<syntaxhighlight lang="egl">record U0 type Exception
end
record U1 type Exception
end
program Exceptions
function main()
foo();
end
function foo()
try
bar();
onException(ex U0)
SysLib.writeStdout("Caught a U0 with message: '" :: ex.message :: "'");
end
bar();
end
function bar()
baz();
end
firstBazCall boolean = true;
function baz()
if(firstBazCall)
firstBazCall = false;
throw new U0{message = "This is the U0 exception"};
else
throw new U1{message = "This is the U1 exception"};
end
end
end</syntaxhighlight>
{{out}}
<pre>
Caught a U0 with message: 'This is the U0 exception'
This is the U1 exception
</pre>
=={{header|Eiffel}}==
Line 775 ⟶ 1,069:
A file called main.e:
<
inherit EXCEPTIONS
Line 812 ⟶ 1,106:
end
end
end</
{{out}}
Line 842 ⟶ 1,136:
Developer exception:</pre>
=={{header|Elena}}==
ELENA
<
class U0
{
constructor new()
<= super new("U0 exception");
}
class U1 : Exception
{
constructor new()
<= super new("U1 exception");
}
singleton Exceptions
{
{
for(i :=
}
}
public program()
{
Exceptions
}</syntaxhighlight>
{{out}}
<pre>
U0 Caught
U1 exception
Call stack:
sandbox'$private'Exceptions.baz[1]:sandbox.l(30)
sandbox'$private'Exceptions.foo[1]:sandbox.l(40)
sandbox'program.function:#invoke:sandbox.l(52)
system'$private'entry.function:#invoke:app.l(5)
system'$private'entrySymbol#sym:app.l(23)
Aborted:ffffffff
</pre>
=={{header|Elixir}}==
<
defmodule U1, do: defexception [:message]
Line 969 ⟶ 1,226:
end
ExceptionsTest.foo</
{{out}}
Line 984 ⟶ 1,241:
=={{header|Erlang}}==
<syntaxhighlight lang="erlang">
-module( exceptions_catch ).
Line 1,004 ⟶ 1,261:
end.
</syntaxhighlight>
{{out}}
<pre>
Line 1,014 ⟶ 1,271:
in call from exceptions_catch:'-task/0-lc$^0/1-0-'/1 (src/exceptions_catch.erl, line 5)
in call from exceptions_catch:'-task/0-lc$^0/1-0-'/1 (src/exceptions_catch.erl, line 5)
</pre>
=={{header|Factor}}==
<syntaxhighlight lang="factor">USING: combinators.extras continuations eval formatting kernel ;
IN: rosetta-code.nested-exceptions
ERROR: U0 ;
ERROR: U1 ;
: baz ( -- )
"IN: rosetta-code.nested-exceptions : baz ( -- ) U1 ;"
( -- ) eval U0 ;
: bar ( -- ) baz ;
: foo ( -- )
[
[ bar ] [
dup T{ U0 } =
[ "%u recovered\n" printf ] [ rethrow ] if
] recover
] twice ;
foo</syntaxhighlight>
{{out}}
<pre>
T{ U0 } recovered
U1
(U) Quotation: [ c-to-factor => ]
Word: c-to-factor
(U) Quotation: [ [ (get-catchstack) push ] dip call => (get-catchstack) pop* ]
(O) Word: command-line-startup
(O) Word: run-script
(O) Word: foo
(O) Word: baz
(O) Word: U1
(O) Method: M\ object throw
(U) Quotation: [
OBJ-CURRENT-THREAD special-object error-thread set-global
current-continuation => error-continuation set-global
[ original-error set-global ] [ rethrow ] bi
]
</pre>
=={{header|Fantom}}==
<
const class U0 : Err
{
Line 1,067 ⟶ 1,367:
}
}
</syntaxhighlight>
{{out}}
Line 1,098 ⟶ 1,398:
=={{header|FreeBASIC}}==
FreeBASIC does not support exceptions or the Try/Catch/Finally statement, as such. However, you can use the Err() function, together with an If (or Switch) statement, to provide somewhat similar functionality:
<
Enum ErrorTypes
Line 1,145 ⟶ 1,445:
Print
Print "Press any key to quit"
Sleep</
{{out}}
Line 1,163 ⟶ 1,463:
The solution here is to define a wrapper, or proxy function, called try.
Function foo calls bar indirectly through try.
<
//
// As all Go programmers should know, the Go authors are sharply critical of
Line 1,265 ⟶ 1,565:
}
trace("complete")
}</
{{out}}
<pre>
Line 1,303 ⟶ 1,603:
</pre>
A simpler example, closer to the task description:
<
import "fmt"
Line 1,361 ⟶ 1,661:
foo()
fmt.Println("No panic")
}</
[http://play.golang.org/p/X2pa8zE1Ce Run in Go Playground].
{{out}}
Line 1,373 ⟶ 1,673:
=={{header|Haskell}}==
<
import Control.Monad.Trans (lift)
Line 1,410 ⟶ 1,710:
case result of
Left e -> putStrLn ("Caught error at top level: " ++ show e)
Right v -> putStrLn ("Return value: " ++ show v)</
{{out}}
Line 1,431 ⟶ 1,731:
not found in languages that natively support exceptions.</i>
<
class U0 : Exception()
Line 1,475 ⟶ 1,775:
initial U0().throw("First exception")
U1().throw("Second exception")
end</
{{out}}
Line 1,494 ⟶ 1,794:
=={{header|Io}}==
<
U1 := Exception clone
Line 1,513 ⟶ 1,813:
)
foo</
{{out}}
<pre>foo caught U0
Line 1,528 ⟶ 1,828:
J leaves most of the implementation of exceptions to the programmer, so:
<
smoutput 'main'
try. foo ''
Line 1,549 ⟶ 1,849:
smoutput ' baz'
type_jthrow_=: 'U',":y throw.
)</
'''Example use:'''
<
main
foo
Line 1,560 ⟶ 1,860:
bar
baz
main caught U1</
=={{header|Java}}==
Line 1,568 ⟶ 1,868:
(or a superclass thereof), unless they are unchecked exceptions
(subclasses of <code>RuntimeException</code> or <code>Error</code>):
<
class U1 extends Exception { }
Line 1,596 ⟶ 1,896:
foo();
}
}</
{{out}}
<pre>
Line 1,623 ⟶ 1,923:
The <code>callee.name</code> property, and the <code>catch(e if ...)</code> statement are Mozilla JavaScript extensions.
<
U.prototype.toString = function(){return this.className;}
Line 1,657 ⟶ 1,957:
}
foo();</
{{out}} from [[Rhino]]:
<pre>caught exception U0
Line 1,664 ⟶ 1,964:
<pre>caught exception U0
uncaught exception: U1</pre>
=={{header|jq}}==
{{works with|jq|>1.4}}
<
def baz(n):
if n==0 then error("U0")
Line 1,679 ⟶ 1,980:
(try bar(1) catch if . == "U0" then "We caught U0" else error(.) end);
foo</
{{out}}
$ jq -n -f Catch_an_exception_thrown_in_a_nested_call.jq
Line 1,688 ⟶ 1,989:
{{works with|Julia|0.6}}
<
struct U1 <: Exception end
Line 1,715 ⟶ 2,016:
end
foo()</
{{out}}
Line 1,725 ⟶ 2,026:
=={{header|Kotlin}}==
<
class U0 : Throwable("U0 occurred")
Line 1,753 ⟶ 2,054:
fun main(args: Array<String>) {
foo()
}</
{{out}}
Line 1,764 ⟶ 2,065:
at ExceptionsKt.main(exceptions.kt:28)
</pre>
=={{header|langur}}==
There is no explicit try block. A catch implicitly wraps the instructions preceding it within a block into a try block.
<syntaxhighlight lang="langur">
val U0 = {"msg": "U0"}
val U1 = {"msg": "U1"}
val baz = fn i: throw if(i==0: U0; U1)
val bar = fn i: baz(i)
val foo = impure fn() {
for i in [0, 1] {
bar(i)
catch {
if _err'msg == U0'msg {
writeln "caught U0 in foo()"
} else {
throw
}
}
}
}
foo()
</syntaxhighlight>
{{out}}
<pre>caught U0 in foo()
VM Errors
general: U1 (baz)</pre>
=={{header|Lasso}}==
Line 1,769 ⟶ 2,101:
but we can easily add one like so.
<
local(
gb = givenblock,
Line 1,808 ⟶ 2,140:
var(bazzed) ? fail('U1') | $bazzed = true
fail('U0')
}</
{{out}}
Line 1,831 ⟶ 2,163:
=={{header|Lua}}==
<
function baz()
if baz_counter==1 then
Line 1,864 ⟶ 2,196:
foo()
</syntaxhighlight>
output:
<pre>lua: errorexample.lua:31: U1
Line 1,875 ⟶ 2,207:
=={{header|Maple}}==
<syntaxhighlight lang="maple">baz := proc( which )
if ( which = 0 ) then
error "U0";
else
end;
end proc:
bar := proc( which )
baz( which );
end proc
foo := proc()
local i;
for i from 0 to 1 do
bar(i);
catch "U0":
end;
end do;
end proc
foo();</syntaxhighlight>
{{out}}
<syntaxhighlight lang="maple">Error, (in baz) U1</syntaxhighlight>
=={{header|Mathematica}} / {{header|Wolfram Language}}==
<
bar[i_] := baz[i];
Line 1,900 ⟶ 2,240:
baz[i_] := Switch[i,
1, Throw["Exception U0 in baz"];,
2, Throw["Exception U1 in baz"];]</
Output:
<pre> foo[]
Line 1,906 ⟶ 2,246:
=={{header|MATLAB}} / {{header|Octave}}==
<
function foo()
Line 1,936 ⟶ 2,276:
foo();
end</
{{out}}
<
message: [1x177 char]
identifier: 'BAZ:U0'
Line 1,947 ⟶ 2,287:
Error in ==> exceptionsCatchNestedCall at 29
foo();</
=={{header|Nemerle}}==
<
using System.Console;
Line 2,000 ⟶ 2,340:
}
}
}</
{{out}}
<pre>Exception U0 caught.
Line 2,010 ⟶ 2,350:
=={{header|Nim}}==
<
type U1 = object of Exception
Line 2,027 ⟶ 2,367:
echo "Function foo caught exception U0"
foo()</
{{out}}
<pre>Function foo caught exception U0
Line 2,039 ⟶ 2,379:
=={{header|Objective-C}}==
<
@end
@interface U1 : NSObject { }
Line 2,081 ⟶ 2,421:
}
return 0;
}</
{{out}}
<pre>
Line 2,090 ⟶ 2,430:
=={{header|OCaml}}==
Exceptions are used everywhere in OCaml, they are easy to write, and they are cheap.
<
exception U1
Line 2,106 ⟶ 2,446:
done
let () = foo ()</
{{out}}
<pre>
Line 2,115 ⟶ 2,455:
=={{header|Oforth}}==
<
Exception Class new: U1
Line 2,125 ⟶ 2,465:
try: e [ 0 bar ] when: [ e isKindOf(U0) ifTrue: [ "Catched" .cr ] else: [ e throw ] ]
try: e [ 1 bar ] when: [ e isKindOf(U0) ifTrue: [ "Catched" .cr ] else: [ e throw ] ]
"Done" . ;</
{{out}}
Line 2,138 ⟶ 2,478:
Exceptions are caught by pattern matching.
<
proc {Foo}
for I in 1..2 do
Line 2,158 ⟶ 2,498:
end
in
{Foo}</
{{out}}
Line 2,173 ⟶ 2,513:
=={{header|PARI/GP}}==
<
U0() = error("x = ", 1, " should not happen!");
Line 2,179 ⟶ 2,519:
baz(x) = if(x==1, U0(), x==2, U1());x;
bar() = baz(call++);
foo() = if(!call, iferr(bar(), E, printf("Caught exception, call=%d",call)), bar())</
Output 1. call to foo():<pre>Caught exception, call=1</pre>
Line 2,195 ⟶ 2,535:
</pre>
Output 3. call to foo():<pre>3</pre>
=={{header|Pascal}}==
Line 2,202 ⟶ 2,541:
=={{header|Perl}}==
Note: Both exceptions are caught and one is re-raised rather than only one being caught.
<
foreach (0..1) {
eval { bar($_) };
Line 2,219 ⟶ 2,558:
}
foo();</
{{out}}
<pre>
Line 2,226 ⟶ 2,565:
...propagated at exceptionsnested.pl line 5.
</pre>
=={{header|Phix}}==
{{libheader|Phix/basics}}
Phix does not have "exception classes" as such, instead you can just throw any string (on it's own) or any integer, optionally
with any (deeply nested) user_data that you like. All exceptions are always caught, however rethrowing is trivial.<br>
As per the discussion for Go, I should say that "bar(); bar();" cannot work - if you catch an exception from the first call,
control resumes within the catch handler, with no way to invoke that second bar(). But a simple loop does the trick.
<!--<syntaxhighlight lang="phix">-->
<span style="color: #008080;">constant</span> <span style="color: #000000;">U0</span> <span style="color: #0000FF;">=</span> <span style="color: #000000;">0<span style="color: #0000FF;">,</span>
<span style="color: #000000;">U1</span> <span style="color: #0000FF;">=</span> <span style="color: #000000;">1</span>
<span style="color: #004080;">integer</span> <span style="color: #000000;">count</span> <span style="color: #0000FF;">=</span> <span style="color: #000000;">0</span>
<span style="color: #008080;">procedure</span> <span style="color: #000000;">baz<span style="color: #0000FF;">(<span style="color: #0000FF;">)</span>
<span style="color: #000000;">count</span> <span style="color: #0000FF;">+=</span> <span style="color: #000000;">1</span>
<span style="color: #008080;">if</span> <span style="color: #000000;">count<span style="color: #0000FF;">=<span style="color: #000000;">1</span> <span style="color: #008080;">then</span>
<span style="color: #008080;">throw<span style="color: #0000FF;">(<span style="color: #000000;">U0<span style="color: #0000FF;">,<span style="color: #0000FF;">{<span style="color: #0000FF;">{<span style="color: #008000;">"any"<span style="color: #0000FF;">,<span style="color: #0000FF;">{<span style="color: #0000FF;">{<span style="color: #008000;">"thing"<span style="color: #0000FF;">}<span style="color: #0000FF;">,<span style="color: #008000;">"you"<span style="color: #0000FF;">}<span style="color: #0000FF;">}<span style="color: #0000FF;">,<span style="color: #008000;">"like"<span style="color: #0000FF;">}<span style="color: #0000FF;">)</span>
<span style="color: #008080;">else</span>
<span style="color: #008080;">throw<span style="color: #0000FF;">(<span style="color: #000000;">U1<span style="color: #0000FF;">)</span>
<span style="color: #008080;">end</span> <span style="color: #008080;">if</span>
<span style="color: #008080;">end</span> <span style="color: #008080;">procedure</span>
<span style="color: #008080;">procedure</span> <span style="color: #000000;">bar<span style="color: #0000FF;">(<span style="color: #0000FF;">)</span>
<span style="color: #000000;">baz<span style="color: #0000FF;">(<span style="color: #0000FF;">)</span>
<span style="color: #008080;">end</span> <span style="color: #008080;">procedure</span>
<span style="color: #008080;">procedure</span> <span style="color: #000000;">foo<span style="color: #0000FF;">(<span style="color: #0000FF;">)</span>
<span style="color: #008080;">for</span> <span style="color: #000000;">i<span style="color: #0000FF;">=<span style="color: #000000;">1</span> <span style="color: #008080;">to</span> <span style="color: #000000;">2</span> <span style="color: #008080;">do</span>
<span style="color:
<span style="color: #000000;">bar<span style="color: #0000FF;">(<span style="color: #0000FF;">)</span>
<span style="color: #008080;">catch</span> <span style="color: #000000;">e</span>
<span style="color: #008080;">if</span> <span style="color: #000000;">e<span style="color: #0000FF;">[<span style="color: #000000;">E_CODE<span style="color: #0000FF;">]<span style="color: #0000FF;">=<span style="color: #000000;">U0</span> <span style="color: #008080;">then</span>
<span style="color: #0000FF;">?<span style="color: #000000;">e<span style="color: #0000FF;">[<span style="color: #000000;">E_USER<span style="color: #0000FF;">]</span>
<span style="color:
<span style="color: #008080;">throw<span style="color: #0000FF;">(<span style="color: #000000;">e<span style="color: #0000FF;">)</span> <span style="color: #000080;font-style:italic;">-- (terminates)</span>
<span style="color: #008080;">end</span> <span style="color: #008080;">if</span>
<span style="color: #008080;">end</span> <span style="color: #008080;">try</span>
<span style="color: #7060A8;">puts<span style="color: #0000FF;">(<span style="color: #000000;">1<span style="color: #0000FF;">,<span style="color: #008000;">"still running...\n"<span style="color: #0000FF;">)</span>
<span style="color: #008080;">end</span> <span style="color: #008080;">for</span>
<span style="color: #7060A8;">puts<span style="color: #0000FF;">(<span style="color: #000000;">1<span style="color: #0000FF;">,<span style="color: #008000;">"not still running...\n"<span style="color: #0000FF;">)</span>
<span style="color: #008080;">end</span> <span style="color: #008080;">procedure</span>
<span style="color: #000000;">foo<span style="color: #0000FF;">(<span style="color: #0000FF;">)
<!--</syntaxhighlight>-->
{{out}}
<pre>
Line 2,310 ⟶ 2,628:
=={{header|PicoLisp}}==
<
(for Tag '(U0 U1)
(catch 'U0
Line 2,322 ⟶ 2,640:
(mapc trace '(foo bar baz))
(foo)</
{{out}}
<pre> foo :
Line 2,334 ⟶ 2,652:
=={{header|PL/I}}==
<syntaxhighlight lang="pl/i">
/* Exceptions: Catch an exception thrown in a nested call */
test: proc options (main);
Line 2,365 ⟶ 2,683:
m = foo();
end test;
</syntaxhighlight>
DESCRIPTION OF EXECUTION:
Line 2,397 ⟶ 2,715:
There is no extra syntax to add to functions and/or methods such as ''bar'',
to say what exceptions they may raise or pass through them:
<
class U1(Exception): pass
Line 2,413 ⟶ 2,731:
raise U1 if i else U0
foo()</
{{out}}
<pre>
Line 2,435 ⟶ 2,753:
through the nested function calls together with the name of the
uncaught exception, (U1) to stderr, then quit the running program.
=={{header|Quackery}}==
<syntaxhighlight lang="quackery"> [ this ] is U0
[ this ] is U1
[ 0 = iff U0 else U1
message put bail ] is baz ( n --> )
[ baz ] is bar ( n --> )
[ 2 times
[ i^
1 backup
bar
bailed if
[ message share
U0 oats iff
[ say "Exception U0 raised." cr
echostack
$ "Press enter to continue"
input drop
message release
drop ]
else [ drop bail ] ] ] ] is foo</syntaxhighlight>
{{out}}
Testing in the Quackery shell, first with trapping the exception U1, and then without trapping the exception U1 (this is bad practice). Before invoking <code>foo</code> we put some arbitrary data on the stack to show if and how it is affected.
<pre>/O> 111 222 333
...
Stack: 111 222 333
/O> 0 backup foo bailed if [ message take echo ]
...
Exception U0 raised.
Stack: 111 222 333 0
Press enter to continue
U1
Stack: 111 222 333
/O> foo
...
Exception U0 raised.
Stack: 111 222 333 0
Press enter to continue
Problem: Cannot remove an immovable item.
Quackery Stack: 111 222 333
Return stack: {[...] 0} {quackery 1} {[...] 11} {shell 5} {quackery 1} {[...] 0} {foo 2} {times 6}
{[...] 10} {[...] 6} {[...] 7} {[...] 1} {bail 1}
/O>
Stack empty.
</pre>
=={{header|R}}==
Line 2,441 ⟶ 2,818:
in your own environment.
See ?new.env and ?get.
<syntaxhighlight lang="r">
number_of_calls_to_baz <- 0
Line 2,457 ⟶ 2,834:
stop(e)
}
</syntaxhighlight>
Example Usage:
<syntaxhighlight lang="r">
foo() # Error: U0
traceback()
</syntaxhighlight>
{{out}}
<pre>
Line 2,474 ⟶ 2,851:
=={{header|Racket}}==
<
#lang racket
Line 2,494 ⟶ 2,871:
(foo)
</syntaxhighlight>
{{out}}
<
Function foo caught exception U0
. . failed 1
</syntaxhighlight>
=={{header|Raku}}==
(formerly Perl 6)
{{trans|Perl}}
<syntaxhighlight lang="raku" line>sub foo() {
for 0..1 -> $i {
bar $i;
CATCH {
when /U0/ { say "Function foo caught exception U0" }
}
}
}
sub bar($i) { baz $i }
sub baz($i) { die "U$i" }
foo;</syntaxhighlight>
{{out}}
<pre>Function foo caught exception U0
U1
in sub baz at catch:12
in sub bar at catch:10
in sub foo at catch:4
in block at catch:14</pre>
=={{header|REXX}}==
Line 2,505 ⟶ 2,907:
<br>This type of exception handling (in REXX) has its limitation
(the label is known global to the program, but not to external subroutines).
<
call foo /*invoke the FOO function (below). */
say 'The REXX mainline program has completed.' /*indicate that Elroy was here. */
Line 2,526 ⟶ 2,928:
/* [↓] this U0 subroutine is ignored.*/
U0: return -1 /*handle exception if not caught. */
U1: return -1 /* " " " " " */</
'''output'''
<pre>
Line 2,534 ⟶ 2,936:
=={{header|Ruby}}==
<
2.times do |i|
begin
Line 2,556 ⟶ 2,958:
class U1 < StandardError; end
foo</
The first call to foo causes the U0 exception. It gets rescued.
The second call results in a U1 exception which is not rescued,
Line 2,569 ⟶ 2,971:
from exception.rb:2:in `foo'
from exception.rb:23:in `<main>'</pre>
=={{header|Rust}}==
Rust has panics, which are similar to exceptions in that they default to unwinding the stack and the unwinding can be caught. However, panics can be configured to simply abort the program and thus cannot be guaranteed to be catchable. Panics should only be used for situations which are truly unexpected. It is prefered to return an Option or Result when a function can fail. <code>Result<T, U></code> is an enum (or sum type) with variants <code>Ok(T)</code> and <code>Err(U)</code>, representing a success value or failure value. <code>main</code> can return a Result, in which case the debug representation of the error will be shown.
<syntaxhighlight lang="rust">#[derive(Debug)]
enum U {
U0(i32),
U1(String),
}
fn baz(i: u8) -> Result<(), U> {
match i {
0 => Err(U::U0(42)),
1 => Err(U::U1("This will be returned from main".into())),
_ => Ok(()),
}
}
fn bar(i: u8) -> Result<(), U> {
baz(i)
}
fn foo() -> Result<(), U> {
for i in 0..2 {
match bar(i) {
Ok(()) => {},
Err(U::U0(n)) => eprintln!("Caught U0 in foo: {}", n),
Err(e) => return Err(e),
}
}
Ok(())
}
fn main() -> Result<(), U> {
foo()
}</syntaxhighlight>
{{out}}
<pre>Caught U0 in foo: 42
Error: U1("This will be returned from main")</pre>
=={{header|Scala}}==
{{libheader|Scala}}
<
class U0 extends Exception
class U1 extends Exception
Line 2,591 ⟶ 3,031:
foo
}
</syntaxhighlight>
Exception U0 is caught, exception U1 is caught and re-thrown.
Program execution is terminated as the U1 exception is not caught
Line 2,600 ⟶ 3,040:
is not [http://seed7.sourceforge.net/manual/errors.htm#Handlers handled]
the program is terminated and a [http://seed7.sourceforge.net/manual/errors.htm#Stack_trace stack trace] is written.
<
const EXCEPTION: U0 is enumlit;
Line 2,635 ⟶ 3,075:
begin
foo;
end func;</
{{out}}
Line 2,653 ⟶ 3,093:
=={{header|Sidef}}==
<
func bar(i) { baz(i) }
func foo {
[0, 1].each { |i|
try { bar(i) }
catch { |
msg ~~ /^U0/
}
}
}
foo()
{{out}}
<pre>
Line 2,675 ⟶ 3,115:
=={{header|Smalltalk}}==
{{works with|GNU Smalltalk}}
<
Exception subclass: #U0.
Exception subclass: #U1.
Line 2,701 ⟶ 3,141:
"Thirds time's a charm..."]
]
</syntaxhighlight>
Running the code:
<syntaxhighlight lang="smalltalk">
st> Foo new foo
'Call to bar was aborted by exception U0'
Line 2,716 ⟶ 3,156:
UndefinedObject>>executeStatements (a String:1)
nil
</syntaxhighlight>
Explanation:<br/>
Line 2,738 ⟶ 3,178:
=={{header|Swift}}==
{{works with|Swift|2.x+}}
<
case U0
case U1
Line 2,765 ⟶ 3,205:
}
try foo()</
{{out}}
<pre>
Line 2,776 ⟶ 3,216:
{{works with|Tcl|8.5}}
<
proc foo {} {
Line 2,801 ⟶ 3,241:
foo
foo</
{{out}}
<pre>$ tclsh85 exceptions.tcl
Line 2,818 ⟶ 3,258:
=={{header|TXR}}==
<
@(defex u1)
@(define baz (x))
Line 2,845 ⟶ 3,285:
@ (end)
@(end)
@(foo)</
{{out|Run}}
Line 2,856 ⟶ 3,296:
1
</pre>
=={{header|uBasic/4tH}}==
uBasic/4tH only captures an exception when a procedure is called by the function TRY(). TRY() returns zero when no exception was thrown. It returns the non-zero errorcode when an exception was thrown. RAISE can only throw user exceptions. If a procedure is called using the normal PROC keyword exceptions are not caught.
<syntaxhighlight lang="uBasic/4tH">u = 0 ' this is U0
v = 1 ' this is U1
Proc _foo ' call foo
End
_foo
For x = u To v ' throw U0 to U1
If x = u ' catch U0
If Try(_bar(x)) Then ' try to execute bar
Print "Procedure foo caught exception U0"
EndIf ' catch exception and write msg
Else ' don't catch other exceptions
Proc _bar(x)
EndIf
Next
Return
_bar
Param (1) ' bar takes a single parameter
Proc _baz(a@) ' bar calls baz
Return
_baz
Param (1) ' baz takes a single parameter
Raise a@ ' baz throws the exception
Return</syntaxhighlight>
{{Out}}
<pre>Procedure foo caught exception U0
Q Exception raised, 16092559880829058:136</pre>
=={{header|Ursala}}==
Line 2,861 ⟶ 3,335:
if baz raises an exception.
The exception is caught or not by foo.
<
baz =
Line 2,879 ⟶ 3,353:
guard(
:/'foo received this result from normal termination of bar:'+ bar,
'U0'?=z/~& :/'foo caught an exception with this error message:')</
Note that the definition of bar includes no conditional (?) or exception
handling operators, and is written without regard for any exceptions.
Line 2,896 ⟶ 3,370:
baz threw a user-defined empty string exception
U1</pre>
=={{header|Visual Basic .NET}}==
<syntaxhighlight lang="vbnet">Class U0
Inherits Exception
End Class
Class U1
Inherits Exception
End Class
Module Program
Sub Main()
Foo()
End Sub
Sub Foo()
Try
Bar()
Bar()
Catch ex As U0
Console.WriteLine(ex.GetType.Name & " caught.")
End Try
End Sub
Sub Bar()
Baz()
End Sub
Sub Baz()
' Static local variable is persisted between calls of the method and is initialized only once.
Static firstCall As Boolean = True
If firstCall Then
firstCall = False
Throw New U0()
Else
Throw New U1()
End If
End Sub
End Module</syntaxhighlight>
Control passes to the Catch block after U0 is thrown, and so the second call to Bar() is not made.
{{out}}
<pre>U0 caught.</pre>
To prevent this, a loop can be used to run the entire Try statement twice:
<syntaxhighlight lang="vbnet"> Sub Foo()
For i = 1 To 2
Try
Bar()
Catch ex As U0
Console.WriteLine(ex.GetType().Name & " caught.")
End Try
Next
End Sub</syntaxhighlight>
{{out}}
<pre>U0 caught.
Unhandled Exception: U1: Exception of type 'U1' was thrown.
at Program.Baz() in Program.vb:line 34
at Program.Bar() in Program.vb:line 25
at Program.Foo() in Program.vb:line 17
at Program.Main() in Program.vb:line 11</pre>
=={{header|Wren}}==
As explained in the [[Exceptions#Wren]] task, Wren doesn't have exceptions as such but we can simulate them by trying to run code which may cause an error in a fiber and then capturing any error that does occur.
We can use that approach here, re-throwing the second (uncaught) exception so that it terminates the script.
<syntaxhighlight lang="wren">var U0 = "U0"
var U1 = "U1"
var bazCalled = 0
var baz = Fn.new {
bazCalled = bazCalled + 1
Fiber.abort( (bazCalled == 1) ? U0 : U1 )
}
var bar = Fn.new {
baz.call()
}
var foo = Fn.new {
for (i in 1..2) {
var f = Fiber.new { bar.call() }
f.try()
var err = f.error
if (err == U0) {
System.print("Caught exception %(err)")
} else if (err == U1) {
Fiber.abort("Uncaught exception %(err) rethrown") // re-throw
}
}
}
foo.call()</syntaxhighlight>
{{out}}
<pre>
Caught exception U0
Uncaught exception U1 rethrown
[./exceptions_nested line 23] in new(_) block argument
[./exceptions_nested line 28] in (script)
</pre>
=={{header|XPL0}}==
The obvious solution is to simply do the catch error handling at the
point where the error is detected. However, XPL0's Restart intrinsic can
be used to do something similar to C++'s catch operation. This technique
avoids having to pass an error condition back up through several levels
of function calls. (Technically, these functions are actually procedures
because they don't return a value, but XPL0 doesn't enforce the
distinction.)
<syntaxhighlight lang "XPL0">func U0; \Exception caused by square root of negative value
real X;
X:= Sqrt(-42.);
func U1; \Exception caused by opening a non-existent file for input
int F;
F:= FOpen("unobtainium.txt", 0);
func Baz;
int CallNo;
[CallNo:= [1]; \static-like variable
if CallNo(0) = 1 then \first time Baz is called
[CallNo(0):= 2;
Text(0, "Calling U0^m^j");
Trap(false); \turn off error trapping to prevent program abort
U0;
Restart;
]
else \second time Baz is called
[Text(0, "Calling U1^m^j");
U1; \error trapping is still disabled
];
];
func Bar;
Baz;
func Foo;
Bar;
int Err;
[Err:= GetErr; \get the exception error after the program is restarted
if Err then \reading GetErr resets any error number to 0, = no error
[Text(0, "Error "); IntOut(0, Err); Text(0, " detected^m^j")];
Foo;
Text(0, "Finished^m^j");
] \second exception is pending, and it will be displayed
</syntaxhighlight>
{{out}}
<pre>
Calling U0
Error 10 detected
Calling U1
Finished
RUN-TIME ERROR 3: I/O
</pre>
=={{header|zkl}}==
<
class U1(Exception.Exception){fcn init{Exception.init("U1")}}
Line 2,904 ⟶ 3,541:
fcn bar(e){baz(e)}
fcn baz(e){throw(e)}
foo()</
{{out}}
<pre>
|