Boost logo

Boost-Commit :

Subject: [Boost-commit] svn:boost r48646 - trunk/tools/jam/doc
From: jurko.gospodnetic_at_[hidden]
Date: 2008-09-07 03:43:43


Author: jurko
Date: 2008-09-07 03:43:43 EDT (Sun, 07 Sep 2008)
New Revision: 48646
URL: http://svn.boost.org/trac/boost/changeset/48646

Log:
Corrected a typo in the Boost Jam documentation. Related paragraph reformatted a bit.
Text files modified:
   trunk/tools/jam/doc/bjam.qbk | 7 ++++++-
   1 files changed, 6 insertions(+), 1 deletions(-)

Modified: trunk/tools/jam/doc/bjam.qbk
==============================================================================
--- trunk/tools/jam/doc/bjam.qbk (original)
+++ trunk/tools/jam/doc/bjam.qbk 2008-09-07 03:43:43 EDT (Sun, 07 Sep 2008)
@@ -853,7 +853,12 @@
 rule FAIL_EXPECTED ( /targets/ * )
 ]
 
-For handling targets whose build actions are expected to fail (e.g. when testing that assertions or compile-time type checkin work properly), Boost Jam supplies the =FAIL_EXPECTED= rule in the same style as =NOCARE=, et. al. During target updating, the return code of the build actions for arguments to =FAIL_EXPECTED= is inverted: if it fails, building of dependent targets continues as though it succeeded. If it succeeds, dependent targets are skipped.
+For handling targets whose build actions are expected to fail (e.g. when testing
+that assertions or compile-time type checking work properly), Boost Jam supplies
+the =FAIL_EXPECTED= rule in the same style as =NOCARE=, et. al. During target
+updating, the return code of the build actions for arguments to =FAIL_EXPECTED=
+is inverted: if it fails, building of dependent targets continues as though it
+succeeded. If it succeeds, dependent targets are skipped.
 
 [endsect]
 


Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk