From c6e658cfcaa2c221aae47d23b47b070a77a97ea7 Mon Sep 17 00:00:00 2001 From: Aleksey Gurtovoy Date: Sun, 28 Nov 2004 04:44:21 +0000 Subject: [PATCH] merge RC_1_32_0 fixes [SVN r26333] --- pyste/doc/introduction.html | 2 +- pyste/doc/policies.html | 2 +- pyste/doc/running_pyste.html | 2 +- pyste/index.html | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/pyste/doc/introduction.html b/pyste/doc/introduction.html index 7d79041a..352aed2e 100644 --- a/pyste/doc/introduction.html +++ b/pyste/doc/introduction.html @@ -33,7 +33,7 @@ GCCXML to parse all the headers and extract the necessary information to automatically generate C++ code.

Example

-Let's borrow the class World from the +Let's borrow the class World from the tutorial: 

     struct World
diff --git a/pyste/doc/policies.html b/pyste/doc/policies.html
index 27ad997c..8061f9b1 100644
--- a/pyste/doc/policies.html
+++ b/pyste/doc/policies.html
@@ -29,7 +29,7 @@ Even thought Pyste can identify various elements in the C++ code, like virtual
 member functions, attributes, and so on, one thing that it can't do is to
 guess the semantics of functions that return pointers or references. In this
 case, the user must manually specify the policy. Policies are explained in the
-
+
 tutorial.

 

 The policies in Pyste are named exactly as in 
diff --git a/pyste/doc/running_pyste.html b/pyste/doc/running_pyste.html
index 10c757a5..5f72e603 100644
--- a/pyste/doc/running_pyste.html
+++ b/pyste/doc/running_pyste.html
@@ -116,7 +116,7 @@ So, the usage is simple enough:

 
>python pyste.py --module=mymodule file.pyste file2.pyste ...

 will generate a file mymodule.cpp in the same dir where the command was
 executed. Now you can compile the file using the same instructions of the
-
+
 tutorial. 

 
Wait... how do I set those I and D flags?

 Don't worry: normally 
diff --git a/pyste/index.html b/pyste/index.html
index c7542d24..55b7d39f 100644
--- a/pyste/index.html
+++ b/pyste/index.html
@@ -3,7 +3,7 @@
 
 Pyste Documentation
 
-
+