diff --git a/doc/reference/using-cpp.xml b/doc/reference/using-cpp.xml
index f26a504f..5400f478 100644
--- a/doc/reference/using-cpp.xml
+++ b/doc/reference/using-cpp.xml
@@ -287,23 +287,23 @@ main( int argc, char **argv )
Extending the C++ interface
- The C++ interface comes in two parts. First, VImage8.h defines a simple
- layer over #GObject for automatic reference counting, then a generic way
- to call any vips8 operation with VImage::call(), then a few convenience
- functions, then a set of overloads.
+ The C++ interface comes in two parts. First, VImage8.h defines a simple
+ layer over #GObject for automatic reference counting, then a generic way
+ to call any vips8 operation with VImage::call(), then a few convenience
+ functions, then a set of overloads.
- The member function for each operation, for example VImage::add(), is
- generated by a small Python program called gen-operators.py
,
- and its companion, gen-operators-h.py
to generate the
- headers. If you write a new VIPS operator, you'll need to rerun these
- programs to make the new member function.
+ The member function for each operation, for example VImage::add(), is
+ generated by a small Python program called gen-operators.py
,
+ and its companion, gen-operators-h.py
to generate the
+ headers. If you write a new VIPS operator, you'll need to rerun these
+ programs to make the new member function.
-
- You can write the wrapper yourself, of course, they are very simple.
- The one for VImage::add() looks like this:
+
+ You can write the wrapper yourself, of course, they are very simple.
+ The one for VImage::add() looks like this:
VImage VImage::add(VImage right, VOption *options)
@@ -317,11 +317,11 @@ VImage VImage::add(VImage right, VOption *options)
set("left", *this) ->
set("right", right));
- return out;
+ return out;
}
- Where VImage::call() is the generic call-a-vips8-operation function.
+ Where VImage::call() is the generic call-a-vips8-operation function.