I also get a compile error when trying to build against the win32-py2.4 release.
src_na_nxutils.c(213) : error C2275: 'PyObject' : illegal use of this type as an expression c:\Python24\include\object.h(104) : see declaration of 'PyObject' src_na_nxutils.c(213) : error C2065: 'ret' : undeclared identifier src_na_nxutils.c(215) : warning C4047: 'return' : 'PyObject *' differs in levels of indirection from 'int'
Do we need to modify our use of the c-api at all?
On 9/5/06, Boyd Waters firstname.lastname@example.org wrote:
Very sorry: here is the initial error: numpy/core/src/arrayobject.c:564: error: 'op' undeclared (first use in this function)
On Sep 5, 2006, at 12:01 AM, Boyd Waters wrote:
1.0b5 Fails to compile?
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da...
Matplotlib-devel mailing list Matplotlibemail@example.com https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
"Charlie" == Charlie Moad firstname.lastname@example.org writes:
Charlie> I also get a compile error when trying to build against Charlie> the win32-py2.4 release. src_na_nxutils.c(213) : error Charlie> C2275: 'PyObject' : illegal use of this type as an Charlie> expression c:\Python24\include\object.h(104) : see
It looks like I made the typical C++ programmer writing C mistake: putting a type declaration in code where it is first used rather than at the beginning of the function. I just committed a change that should fix this.