[Mockpp-commits] mockpp/mockpp/docs/en appendix.docbook,1.9,1.10 dev_production.docbook,1.3,1.4
Brought to you by:
ewald-arnold
From: Ewald A. <ewa...@us...> - 2005-05-21 14:18:00
|
Update of /cvsroot/mockpp/mockpp/mockpp/docs/en In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv25124/mockpp/docs/en Modified Files: appendix.docbook dev_production.docbook Log Message: release1.8.1 Index: appendix.docbook =================================================================== RCS file: /cvsroot/mockpp/mockpp/mockpp/docs/en/appendix.docbook,v retrieving revision 1.9 retrieving revision 1.10 diff -u -d -r1.9 -r1.10 --- appendix.docbook 7 May 2005 17:00:56 -0000 1.9 +++ appendix.docbook 21 May 2005 14:17:50 -0000 1.10 @@ -73,8 +73,8 @@ <!-- ===================================== --> -<sect2 id="generating-rpms"> -<title>Installing on systems using autoconf and friends</title> +<sect2 id="creating-rpms"> +<title>Creating and Installing an RPM</title> <para>Using the previous installation procedure has drawacks when you want do uninstall or upgrade to a newer version. Maybe you rather want to benefit Index: dev_production.docbook =================================================================== RCS file: /cvsroot/mockpp/mockpp/mockpp/docs/en/dev_production.docbook,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- dev_production.docbook 6 May 2005 12:40:30 -0000 1.3 +++ dev_production.docbook 21 May 2005 14:17:50 -0000 1.4 @@ -56,7 +56,7 @@ code. Since variables are very internal you should not try to make them accessible somehow. The following sections show some patterns how to use member methods to intentionally grant access to parts which are actually - internal. </para> + internal.</para> <sect3> <title>Lifting class members</title> @@ -102,8 +102,8 @@ via getter and setter methods. If you make such methods <keysym>private</keysym> and <keysym>virtual</keysym> you prevent its direct use but still have the chance to overload the getter method in - the tests. This way it is possible to insert mock objects for internal - variables.</para> + the tests. This way it is possible to insert mock objects to replace + internal variables.</para> <para><programlisting>class Sample { |