* Updated chapter 3.3 (bug #2053018)

git-svn-id: svn+ssh://svn.code.sf.net/p/check/code/trunk@438 64e312b2-a51f-0410-8e61-82d0ca0eb02a

diff --git a/doc/check.texi b/doc/check.texi
index ed510d909c43a3ecaa93fc4f3ac66c7357e57dc4..efaf18fe4db618271b514bdeaedd8ab31c37164b 100644 (file)
--- a/doc/check.texi
+++ b/doc/check.texi
@@ -490,12 +490,12 @@ Here are the changes to @file{check_money.c} for our first unit test:
 A unit test should just chug along and complete.  If it exits early,
 or is signaled, it will fail with a generic error message.  (Note: it
 is conceivable that you expect an early exit, or a signal.  There is
-currently nothing in Check to specifically assert that we should
-expect either --- if that is valuable, it may be worth while adding to
-Check.)  If we want to get some information about what failed, we need
-to use the @code{fail_unless()} function.  The function (actually a
-macro) takes a first Boolean argument, and an error message to send if
-the condition is not true.
+functionality in Check to specifically assert that we should expect a
+signal, but early exits are currently not handled -- if that is valuable,
+it may be worth while adding to Check.)  If we want to get some information
+about what failed, we need to use the @code{fail_unless()} function.  The
+function (actually a macro) takes a first Boolean argument, and an error
+message to send if the condition is not true.
 
 @findex fail()
 If the Boolean argument is too complicated to elegantly express within