Recent changes to bugs

C to C call doesn't work

Anonymous — Fri, 30 Jul 2004 04:44:06 -0000

A call from a C function to another raises an error.

import PyInline
pyin = PyInline.build(code = """
#include <stdio.h>
double f(double x){return x;}
double g(double x){return f(x);}
""", language = "C")
print pyin.g(0.1)

gives

Traceback (most recent call last):
File "testpyin.py", line 18, in ?
""", language = "C")
File "PyInline\__init__.py",
line 38, in build
return b.build()
File "PyInline\C.py", line 40
, in build
self._parse()
File "PyInline\C.py", line 92
, in _parse
d['params'] = self._parseParams(d['rawparams'])
File "PyInline\C.py", line 11
0, in _parseParams
return [self._parseParam(p) for p in rawparams]
File "PyInline\C.py", line 11
8, in _parseParam
raise BuildError("Error parsing parameter %s" % p)
PyInline.BuildError: Error parsing parameter x

newline gives an error with gcc

Anonymous — Mon, 12 Jul 2004 04:18:46 -0000

A string with a newline gives an error.

printf("hello\n");

becomes (in _PyInline_...c)

printf("hello
");

which gives an error from gcc

error: missing terminating "".... etc

so it won't work with cygwin gcc (newest); somehow my
mingw gcc (older version) allows compilation.

suppress a couple gcc warnings

Skip Montanaro — Wed, 29 Aug 2001 14:59:39 -0000

Ken,

When I ran your examples, gcc complained about the
init function not being a prototype and the generated
.c file not ending with a newline. Here's a patch
that gets rid of those warnings.