Ensure that we have only a single SWIG_CException_Raise() function across all modules instead of having per-module functions and, worse, per-module PendingException variables, which resulted in compile-time errors and couldn't work anyhow because function checking for the current exception didn't necessarily use the same "global" variable where it was stored. More formally, old version resulted in ODR violations and undefined behaviour. The way we avoid it now is rather ugly and consists in excluding SWIG_CException from wrapping using the hack in the source code which postpones wrapping this class until the very end and checks if we had encountered any %import directives and simply doesn't wrap it if we did. The same code is used to define the special SWIG_CException_DEFINED preprocessor symbol which is then used in the generated code to prevent the SWIG_CException class declaration from being compiled as part of the wrapper too (because this still happens due to %inline being used for its definition, and there doesn't seem to be any better way to avoid this). This is definitely not pretty, but at least adding "throw(char*)" to a couple of functions in mod_[ab].i test suite files works now instead of failing (even without linking and running) as before. This commit doesn't modify the test suite to avoid possible problems with the other languages, however. |
||
|---|---|---|
| .. | ||
| allocate.cxx | ||
| browser.cxx | ||
| c.cxx | ||
| cffi.cxx | ||
| contract.cxx | ||
| csharp.cxx | ||
| d.cxx | ||
| directors.cxx | ||
| emit.cxx | ||
| go.cxx | ||
| guile.cxx | ||
| interface.cxx | ||
| java.cxx | ||
| javascript.cxx | ||
| lang.cxx | ||
| lua.cxx | ||
| main.cxx | ||
| mzscheme.cxx | ||
| nested.cxx | ||
| ocaml.cxx | ||
| octave.cxx | ||
| overload.cxx | ||
| perl5.cxx | ||
| php.cxx | ||
| python.cxx | ||
| r.cxx | ||
| README | ||
| ruby.cxx | ||
| scilab.cxx | ||
| swigmain.cxx | ||
| swigmod.h | ||
| tcl8.cxx | ||
| typepass.cxx | ||
| utils.cxx | ||
| xml.cxx | ||
06/25/2002 This directory contains all of the SWIG language modules. Many of these modules contain code that dates back to SWIG1.0. The module API has changed a lot in the development releases so this is fairly messy. We're working on cleaning it up, but you'll have to bear with us until it's done. -- Dave