diff --git a/doc/cross_module_dependencies.html b/doc/cross_module_dependencies.html index 0508cf6e..cd0cc02d 100644 --- a/doc/cross_module_dependencies.html +++ b/doc/cross_module_dependencies.html @@ -77,8 +77,9 @@ way with the class_builder<> template. To also enable the automatic conversion of std::vector<double> function arguments or return values in other Boost.Python C++ modules, the converters that convert a std::vector<double> C++ object -to a Python object and vice versa (see last section for details) have -to be exported. For example: +to a Python object and vice versa (i.e. the to_python() and +from_python() template functions) have to be exported. For +example:
class_builder<std::vector<double> > v_double(std_vector_module, "double"); @@ -129,8 +130,8 @@ class_builder<store> py_store(your_module, "store"); export_converters_noncopyable(py_store);-The corresponding import_converters() statement does not need -any special attention: +The corresponding import_converters<> statement does not +need any special attention:
import_converters<store> py_store("noncopyable_export", "store");
@@ -158,8 +159,8 @@ search path (sys.path).
The situation is not always this obvious. Suppose the
-statistics module has a random function that returns a vector
-of random numbers with a given length:
+statistics module has a random() function that
+returns a vector of random numbers with a given length:
import statistics
@@ -244,7 +245,7 @@ If a library is wrapped that consists of both header files and compiled
components (e.g. libdvect.a, dvect.lib, etc.), both
the Boost.Python extension module with the
export_converters() statement and the module with the
-import_converters() statement need to be linked against
+import_converters<> statement need to be linked against
the object library. Ideally one would build a shared library (e.g.
libdvect.so, dvect.dll, etc.). However, this
introduces the issue of getting the search path for the dynamic loading
@@ -292,5 +293,4 @@ suitability for any purpose.
Updated: March 2001
-