0295bd6b3f
The general agreement in the project is that c++ exception specs are pointless and add bloat in production code. See also this rant for more background: http://drdobbs.com/cpp/184401544 This removes the code that generates the exception specs on the generated c++ headers, and fixes up the few places that broke subsequently because of widening exception specs, which in turn was due to the rather unfortunate decision to not have a virtual dtor in XInterface. Change-Id: I60db26e1cc4d4fe6eeef5975e39497841e92588a |
||
|---|---|---|
| .. | ||
| inc/codemaker | ||
| prj | ||
| source | ||
| test/javamaker | ||
| Executable_cppumaker.mk | ||
| Executable_javamaker.mk | ||
| Makefile | ||
| Module_codemaker.mk | ||
| Package_inc.mk | ||
| README | ||
| StaticLibrary_codemaker.mk | ||
| StaticLibrary_codemaker_cpp.mk | ||
| StaticLibrary_codemaker_java.mk | ||
UNO interface declaration/stub generators for: - C++: cppumaker generates headers (.hpp and .hdl files) that provide the UNO API C++ binding - Java: javamaker generates class files that provide the JVM UNO API binding - the one for .Net is in module cli_ure Note the different terminology used by cppumaker vs. gbuild for the three variants that can be generated by cppumaker for some of the inline functions: (10:21:49) sberg: tml_, switch: -L; cpputype.cxx: light; gbuild: normal (10:22:02) sberg: tml_, switch: none; cpputype.cxx: normal; gbuild: bootstrap (10:22:20) sberg: tml_, switch: -C; cpputype.cxx: comprehensive; gbuild: comprehensive (10:22:45) sberg: ...a recipe for confusion