From 3c89ad78eb3158a49509ac86152195fb1f6ea8e5 Mon Sep 17 00:00:00 2001 From: def Date: Sat, 21 Jun 2014 13:42:29 +0200 Subject: [PATCH] Rename {.effect.} to {.effects.} in Tut 2 --- doc/tut2.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/tut2.txt b/doc/tut2.txt index 11b485f507..1e23618e08 100644 --- a/doc/tut2.txt +++ b/doc/tut2.txt @@ -501,7 +501,7 @@ with the file and line where the uncaught exception is being raised, which may help you locate the offending code which has changed. If you want to add the ``{.raises.}`` pragma to existing code, the compiler can -also help you. You can add the ``{.effect.}`` pragma statement to your proc and +also help you. You can add the ``{.effects.}`` pragma statement to your proc and the compiler will output all inferred effects up to that point (exception tracking is part of Nimrod's effect system). Another more roundabout way to find out the list of exceptions raised by a proc is to use the Nimrod ``doc2``