-
$ cat test.hpp
class test
{
public:
typedef enum
{
XXX
} valueType;
typedef struct
{
valueType t;
} s;
valueType myfunc (void);
};
$ cat test.i
%module test
%{
#include "test.hpp"
%}
%include test.hpp
$ swig -c++ -python test.i
$ g++ test_wrap.cxx -c -I/usr/include/python2.6
test_wrap.cxx:2801...
2009-09-30 12:04:45 UTC in SWIG
-
The issue is that WCHAR_MAX and WINT_MAX need to be litteral constants; so, UINT16_MAX is fine (it's itself defined as a litteral) but "((wchar_t) -1)" is not, because it's not a litteral constant, it's a constant expression.
2009-07-31 08:27:12 UTC in MinGW-w64 - for 32 and 64 bit Windows
-
Yep, the CVS version is exactly as I proposed in my patch, sorry for that.
2009-07-31 07:19:04 UTC in MinGW - Minimalist GNU for Windows
-
For int_fast8_t, it needs to be signed whether or not "char" is signed. So, it needs to be explicitly defined as "signed char". (There are three "char" types: "char", "signed char" and "unsigned char"; at compilation, "char" happens to be signed or unsigned, but it is still a different type than "signed char" and "unsigned char".) Also, I've checked with a cross-compiler that it fixes both...
2009-07-31 07:09:27 UTC in MinGW-w64 - for 32 and 64 bit Windows
-
I've reported this over at mingw32, and I think it also applies to mingw-w64:
https://sourceforge.net/tracker/?func=detail&aid=2829951&group_id=2435&atid=302435.
2009-07-30 22:19:33 UTC in MinGW-w64 - for 32 and 64 bit Windows
-
GCC-4.5 has good coverage of the C99 types in stdint.h, and it currently has three failures on mingw32 (gcc.dg/c99-stdint-{1,5,6}.c), due to two issues:
1. int_fast8_t is defined as "char" instead of being "signed char" (as are int_least8_t and int8_t); this is potentially troublesome if one plays with char signedness; also, this is contrary to all headers I could find (except in those that...
2009-07-30 22:11:22 UTC in MinGW - Minimalist GNU for Windows
-
Patch was commited to binutils mainline on 2009-06-09. I think this issue should be closed.
2009-07-14 19:44:56 UTC in MinGW - Minimalist GNU for Windows
-
In the GNU Fortran runtime library (libgfortran), DTIME and ETIME rely on the same system calls to obtain timing information, so I wonder why one would work and not the other.
The difference between ETIME (http://gcc.gnu.org/onlinedocs/gfortran/ETIME.html) and DTIME (http://gcc.gnu.org/onlinedocs/gfortran/DTIME.html) is that ETIME reports time since start of process, and DTIME reports time...
2009-07-14 19:43:48 UTC in MinGW - Minimalist GNU for Windows
-
This GCC bug was fixed for trunk (4.5) and 4.4 branch.
2009-07-14 19:32:45 UTC in MinGW - Minimalist GNU for Windows
