Update of /cvsroot/mockpp/mockpp/mockpp/docs/en
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv23273/mockpp/docs/en
Modified Files:
dev_embedded.docbook
Log Message:
two sections
Index: dev_embedded.docbook
===================================================================
RCS file: /cvsroot/mockpp/mockpp/mockpp/docs/en/dev_embedded.docbook,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- dev_embedded.docbook 3 Dec 2005 18:13:14 -0000 1.4
+++ dev_embedded.docbook 7 Dec 2005 19:49:00 -0000 1.5
@@ -1,10 +1,13 @@
<sect1 id="embedded-systems">
<title>Working With Embedded Systems</title>
+<sect2 id="embedded-problem">
+<title>The Problem</title>
+
<para>There are hidden costs concerning memory resources when programming in
C++. On a desktop system with plenty of virtual memory you don't neccessarily
recognize it. But working with embedded systems is different as there is only a
-limited amout of physical ram available.</para>
+limited amout of physical memory available.</para>
<para>For that reasons it is important to know the places where he compiler adds
additional code:
@@ -39,7 +42,7 @@
compiled with different settings. The size ranged from around 320KiB with the
default settings down to 180KiB with as many features disabled as possible.
-<table><title>Proportion of Important Features</title>
+<table><title>Memory Consumption of C++ Code</title>
<tgroup cols='3' align='left' colsep='1' rowsep='1'>
<thead>
<row>
@@ -69,7 +72,12 @@
</para>
-<para>Disabling RTTI in mockpp; has little consequences. It is only used for a
+</sect2>
+
+<sect2 id="embedded-solution">
+<title>The Solution</title>
+
+<para>Disabling RTTI in &mockpp; has little consequences. It is only used for a
few diagnostic messages. In the worst case you might have to search for the
problematic class.</para>
@@ -112,4 +120,5 @@
</para>
+</sect2>
</sect1>
|
