diff --git a/Doc/Manual/Python.html b/Doc/Manual/Python.html index 3f0193cc3..0a0bed213 100644 --- a/Doc/Manual/Python.html +++ b/Doc/Manual/Python.html @@ -2007,7 +2007,7 @@ public: For each class that has directors enabled, SWIG generates a new class that derives from both the class in question and a special -__DIRECTOR__ class. These new classes, referred to as director +Swig::Director class. These new classes, referred to as director classes, can be loosely thought of as the C++ equivalent of the Python proxy classes. The director classes store a pointer to their underlying Python object and handle various issues related to object ownership. @@ -2015,7 +2015,7 @@ Indeed, this is quite similar to the "this" and "thisown" members of the Python proxy classes.
-For simplicity let's ignore the __DIRECTOR__ class and refer to the +For simplicity let's ignore the Swig::Director class and refer to the original C++ class as the director's base class. By default, a director class extends all virtual methods in the inheritance chain of its base class (see the preceding section for how to modify this behavior). @@ -2150,7 +2150,7 @@ suffice in most cases:
%feature("director:except") {
if ($error != NULL) {
- throw SWIG_DIRECTOR_METHOD_EXCEPTION();
+ throw Swig::DirectorMethodException();
}
}
@@ -2160,7 +2160,7 @@ This code will check the Python error state after each method call from
a director into Python, and throw a C++ exception if an error occured.
This exception can be caught in C++ to implement an error handler.
Currently no information about the Python error is stored in the
-SWIG_DIRECTOR_METHOD_EXCEPTION object, but this will likely change in
+Swig::DirectorMethodException object, but this will likely change in
the future.
@@ -2176,15 +2176,15 @@ suitable exception handler:
%exception {
try { $action }
- catch (SWIG_DIRECTOR_EXCEPTION &e) { SWIG_fail; }
+ catch (Swig::DirectorException &e) { SWIG_fail; }
}
-The class SWIG_DIRECTOR_EXCEPTION used in this example is actually a
-base class of SWIG_DIRECTOR_METHOD_EXCEPTION, so it will trap this
+The class Swig::DirectorException used in this example is actually a
+base class of Swig::DirectorMethodException, so it will trap this
exception. Because the Python error state is still set when
-SWIG_DIRECTOR_METHOD_EXCEPTION is thrown, Python will register the
+Swig::DirectorMethodException is thrown, Python will register the
exception as soon as the C wrapper function returns.
%feature("director:except") {
- throw SWIG_DIRECTOR_METHOD_EXCEPTION($error);
+ throw Swig::DirectorMethodException($error);
}
@@ -3090,4 +3090,4 @@ for more details).
SWIG 1.3 - Last Modified : $Date$