[Cppunit-cvs] cppunit/doc Money.dox,1.2,1.3

[Baptiste L. <bl...@us...>]

Update of /cvsroot/cppunit/cppunit/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19551

Modified Files:
	Money.dox 
Log Message:
* fixed a bunch of typos reported by Dave Dibble.

Index: Money.dox
===================================================================
RCS file: /cvsroot/cppunit/cppunit/doc/Money.dox,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3
*** Money.dox	5 Jul 2005 20:14:14 -0000	1.2
--- Money.dox	5 Jul 2005 20:56:09 -0000	1.3
***************
*** 32,36 ****
  - The resulting libraries can be found in the $CPPUNIT/lib/ directory.
  
! Once it is done, you need to tell VC++ where are the includes and librairies
  to use them in other projects. Open the 'Tools/Options...' dialog, and in the
  'Directories' tab, select 'include files' in the combo. Add a new entry that
--- 32,36 ----
  - The resulting libraries can be found in the $CPPUNIT/lib/ directory.
  
! Once it is done, you need to tell VC++ where are the includes and libraries
  to use them in other projects. Open the 'Tools/Options...' dialog, and in the
  'Directories' tab, select 'include files' in the combo. Add a new entry that
***************
*** 94,98 ****
  \section sec_running_test Running our tests
  
! We have a main that doesn't do anything. Let's start by adding the mecanics
  to run our tests (remember, test before you code ;-) ). For this example, 
  we will use a TextTestRunner with the CompilerOutputter for post-build 
--- 94,98 ----
  \section sec_running_test Running our tests
  
! We have a main that doesn't do anything. Let's start by adding the mechanics
  to run our tests (remember, test before you code ;-) ). For this example, 
  we will use a TextTestRunner with the CompilerOutputter for post-build 
***************
*** 155,159 ****
  - Select 'All configurations' (upper left combo)
  - In the 'Post-build description', enter 'Unit testing...'
! - In 'post-build command(s)', add a new line: <tt>\$(TargetPath)$</tt>
  
  <tt>\$(TargetPath)</tt> expands into the name of your application:
--- 155,159 ----
  - Select 'All configurations' (upper left combo)
  - In the 'Post-build description', enter 'Unit testing...'
! - In 'post-build command(s)', add a new line: <tt>\$(TargetPath)</tt>
  
  <tt>\$(TargetPath)</tt> expands into the name of your application:
***************
*** 167,171 ****
  step failed.
  
! Compile. Notices that the application's output is now in the build window.
  How convenient!
  
--- 167,171 ----
  step failed.
  
! Compile. Notice that the application's output is now in the build window.
  How convenient!
  
***************
*** 291,295 ****
  
  Well, we finally have a good start of what our Money class will
! look likes. Let's start implementing...
  
  <tt>Money.h</tt>
--- 291,295 ----
  
  Well, we finally have a good start of what our Money class will
! look like. Let's start implementing...
  
  <tt>Money.h</tt>
***************
*** 332,336 ****
  indicates that string is not equal to expected value. There is only
  two ways for this to happen: the member was badly initialized or we
! returned the wrong value. After a quick check, we fin out it is the former.
  Let's fix that:
  
--- 332,336 ----
  indicates that string is not equal to expected value. There is only
  two ways for this to happen: the member was badly initialized or we
! returned the wrong value. After a quick check, we find out it is the former.
  Let's fix that:
  
***************
*** 344,348 ****
  
  Compile. Our test finally pass!
! Let's add some functionnalities to our Money class.
  
  
--- 344,348 ----
  
  Compile. Our test finally pass!
! Let's add some functionnality to our Money class.
  
  
***************
*** 418,422 ****
    }\endcode
  
! Compile, run. Finaly got it working!
  
  
--- 418,422 ----
    }\endcode
  
! Compile, run. Finally got it working!
  
  
***************
*** 489,493 ****
  };\endcode
  
! By convention, you ends the name of such tests with \c 'Throw', that way, you
  know that the test expect an exception to be thrown. Let's write our test case:
  
--- 489,493 ----
  };\endcode
  
! By convention, you end the name of such tests with \c 'Throw', that way, you
  know that the test expect an exception to be thrown. Let's write our test case:
  
***************
*** 535,542 ****
    }\endcode
  
!   Compile. Our test finaly pass!
  
    TODO:
! - Copy constructor/Assigment operator
  - Introducing fixtures
  - ?
--- 535,542 ----
    }\endcode
  
!   Compile. Our test finaly passes!
  
    TODO:
! - Copy constructor/Assignment operator
  - Introducing fixtures
  - ?