diff --git a/Doc/Manual/Contents.html b/Doc/Manual/Contents.html index a315096a5..47f7ec449 100644 --- a/Doc/Manual/Contents.html +++ b/Doc/Manual/Contents.html @@ -229,6 +229,7 @@
Sometimes, it may be neccesary to add your own special functions, which bypass the normal SWIG wrappering method, and just use the native lua-c API calls. These 'native' functions allow direct adding of your own code into the module. This is performed with the %native directive as follows:
diff --git a/Doc/Manual/Ruby.html b/Doc/Manual/Ruby.html index 3dd61012a..5605a78f7 100644 --- a/Doc/Manual/Ruby.html +++ b/Doc/Manual/Ruby.html @@ -26,1018 +26,42 @@ -This chapter describes SWIG's support of Ruby.
-SWIG 1.3 is known to work with Ruby versions 1.6 and later. @@ -1060,10 +84,7 @@ of Ruby.
-To build a Ruby module, run SWIG using the -ruby @@ -1691,10 +712,7 @@ declarations in your SWIG interface files to Ruby constructs.
-The SWIG %module directive specifies @@ -1863,10 +881,7 @@ Ruby's built-in names.
-Global functions are wrapped as Ruby module methods. For @@ -2033,10 +1048,7 @@ effect until it is explicitly disabled using %mutable. -
C/C++ constants are wrapped as module constants initialized @@ -2080,10 +1092,7 @@ constant values, e.g.
-"Opaque" pointers to arbitrary C/C++ types (i.e. types that @@ -2135,10 +1144,7 @@ the Ruby nil object.
-C/C++ structs are wrapped as Ruby classes, with accessor @@ -2313,10 +1319,7 @@ pointers. For example,
-Like structs, C++ classes are wrapped by creating a new Ruby @@ -3915,10 +2918,7 @@ caught here and a C++ exception is raised in its place.
-Ruby has several common naming conventions. Constants are @@ -4203,10 +3203,7 @@ Features") for more details).
-Ruby methods that modify an object in-place and end in an @@ -5726,10 +4723,7 @@ providing for a more natural integration between C++ code and Ruby code.
-This section describes how you can modify SWIG's default @@ -8489,10 +7483,7 @@ for VALUE -
void rb_raise(VALUE exception, const char *fmt,
@@ -8659,10 +7650,7 @@ arguments are interpreted as with printf().
-30.7.8.5 Iterators
-
-
-
+30.3.0.2 Iterators
void rb_iter_break()
diff --git a/Doc/Manual/SWIGPlus.html b/Doc/Manual/SWIGPlus.html index 16ef7fdc7..ba10455b1 100644 --- a/Doc/Manual/SWIGPlus.html +++ b/Doc/Manual/SWIGPlus.html @@ -49,6 +49,7 @@As has been mentioned, when %rename includes parameters, the parameter types must match exactly (no typedef or namespace resolution is performed). SWIG treats templated types slightly differently and has an additional matching rule so unlike non-templated types, an exact match is not always required. @@ -4124,7 +4127,7 @@ namespace Space { -
@@ -4175,7 +4178,7 @@ Consult the "Exception handling with %exc The next section details a way of simulating an exception specification or replacing an existing one.
-@@ -4225,7 +4228,7 @@ just a single catch handler for the base class, EBase will be generated
-@@ -4275,7 +4278,7 @@ when checking types. However, no such support is currently provided for member pointers.
-@@ -4485,7 +4488,7 @@ p = f.__deref__() # Raw pointer from operator->
-@@ -4648,7 +4651,7 @@ public: -
@@ -4739,7 +4742,7 @@ typedef Outer::Inner Inner; The downside to this approach is having to maintain two definitions of Inner, the real one and the one in the interface file that SWIG parses.
-@@ -4797,7 +4800,7 @@ using another tool if maintaining constness is the most important part of your project.
-