Hi
2011/4/14 Mark Hammond <[email protected]>:
> Yeah - this is a bug in the general DWORD handling in SWIG generated files.
> I'm not sure how to tell SWIG to use a different format char, but I have
> managed to work around it in other ways which is good for the general case.
With the old SWIG-1.1, the format char is hardcoded in the cpp source of SWIG
(in Modules/Python.cxx)::
case T_LONG : case T_ULONG: case T_SLONG :
parse_args << "l";
break;
which is wrong of course.
Was it ever considered using a newer version of Swig?
--
Amaury Forgeot d'Arc
_______________________________________________
python-win32 mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-win32
