e2b60d3b10
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@7347 626c5289-ae23-0410-ae9c-e8d60b6d4f22
89 lines
3.9 KiB
Text
89 lines
3.9 KiB
Text
Version 1.3.26 (in progress)
|
|
============================
|
|
|
|
07/22/2005: wsfulton
|
|
[C#] Changes to support C# structs returned by value. The changes required are:
|
|
- Using an optional 'null' attribute in the out typemap. If this attribute is specified,
|
|
then it is used for the $null special variable substitution.
|
|
- The ctype used in the C/C++ wrappers is no longer initialised to 0 on declaration.
|
|
Both of these changes fix the situations where an attempt was made to assign 0 to the
|
|
returned struct. Marshalling structs as value types still requires user defined typemaps.
|
|
See documentation for an example.
|
|
|
|
07/22/2005: wsfulton
|
|
[C#, Java] Fix SWIG_exception usage to work with compilers that don't support empty macro
|
|
arguments. Unfortunately this fix will stop usage of SWIG_exception being used within typemaps
|
|
that use "" or %{ %} delimeters, but continues to work with typemaps using {} delimeters.
|
|
Please use the SWIG_CSharpSetPendingExceptionArgument or SWIG_JavaThrowException methods instead
|
|
as SWIG_exception is really intended as a platform independent macro for the SWIG library writers.
|
|
|
|
07/16/2005: mkoeppe
|
|
[Allegro CL] Use specific foreign types rather than (* :void).
|
|
Use *swig-identifier-converter*.
|
|
|
|
06/27/2005: wsfulton
|
|
Functions declared as 'extern' no longer have an additional function declaration added to the
|
|
wrapper files. There are some cases where SWIG does not get this right, eg bug #1205859 (extern
|
|
functions with default arguments declared in a namespace). Also SWIG cannot get non-standard
|
|
calling conventions correct, eg Windows calling conventions are usually handled like this:
|
|
|
|
%{
|
|
#define DLLIMPORT __declspec(dllimport)
|
|
#define STDCALL __stdcall
|
|
%}
|
|
#define DLLIMPORT
|
|
#define STDCALL
|
|
%inline %{
|
|
DLLIMPORT extern STDCALL void function(int);
|
|
%}
|
|
|
|
SWIG incorrectly generates:
|
|
|
|
extern void function(int);
|
|
|
|
To which there is no solution as SWIG doesn't handle non-standard calling conventions. The extra
|
|
'extern' function that SWIG generates is superfluous unless a user has forgotten to add the function
|
|
declaration into the wrappers.
|
|
|
|
The -noextern commandline argument is now redundant and a new commandline argument -addextern can
|
|
be used to obtain the original behaviour. This shouldn't be necessary unless the header file
|
|
containing the function declaration was inadvertently not added to the wrappers. To fix this
|
|
add the function declaration into your wrappers, For example, replace:
|
|
|
|
extern void foo(int);
|
|
|
|
with:
|
|
|
|
%inline %{
|
|
extern void foo(int);
|
|
%}
|
|
|
|
*** POTENTIAL INCOMPATIBILITY ***
|
|
|
|
06/22/2005: wsfulton
|
|
[C#, Java, Modula3, Ocaml]
|
|
The intermediary function names have been changed when wrapping variables to
|
|
match the other language modules so that %extend for a member variable works
|
|
uniformly across all language modules, eg:
|
|
|
|
%extend ExtendMe {
|
|
Var;
|
|
};
|
|
|
|
%{
|
|
void ExtendMe_Var_set(ExtendMe *, double) {...}
|
|
double ExtendMe_Var_get(ExtendMe *) {...}
|
|
%}
|
|
|
|
The methods implementing the get/set used to be:
|
|
|
|
%{
|
|
void set_ExtendMe_Var(ExtendMe *, double) {...}
|
|
double get_ExtendMe_Var(ExtendMe *) {...}
|
|
%}
|
|
|
|
This also changes the name of variable wrapper functions when using -noproxy.
|
|
The original names can be generated with the -oldvarnames commandline option.
|
|
|
|
*** POTENTIAL INCOMPATIBILITY ***
|
|
|