warn message in log summary

Lisandro Dalcin dalcinl at gmail.com
Fri Dec 7 17:32:03 CST 2007

On 12/7/07, Brad Aagaard <baagaard at usgs.gov> wrote:
> The main problem is that we chose Pyrex to do the bindings instead of SWIG.

I see

> Pyrex is based on C, not C++ so we had to wrap the C++ code in C for Pyrex.

Of course, no other way

> Using Pyrex was a mistake. We plan to switch to SWIG in the next few months.

Indeed.  Feel free to ask me in the future in case you do not know
much about SWIG or have any trouble. The only big deal I see for
robust wrapping of C++ with SWIG for using from Python, is that you
really need a reference counting machinery for your C++ clases. And
then SWIG can be told to call incref()/decref() methods in your C++
instances were needed.

Lisandro Dalcín
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594

More information about the petsc-dev mailing list