Mailman 3 Another problem with split_module - Cplusplus-sig

Sept. 26, 2006

      Hi Roman,

as you may remember I'm generating function wrappers for functions
expecting pointers to callback functions along with an instance pointer
of type void.
How do I make sure these wrappers are generated to the same file as the
registration of the wrapper?

Consider the following test:
In single file mode this produces a working test module.
In split file mode the WRAPPER_CODE is generated to
test_wrapper.main.cpp whereas the registration is generated to
test_wrapper_free_functions.pypp.cpp.

test.hpp
--- 8>< ------ ><8 ---
void test (void *instance, void (*callback)(void *));
--- 8>< ------ ><8 ---

test.py
--- 8>< ------ ><8 ---
#
# Wrapper code for void test (void (*test)(void *));
#
WRAPPER_CODE = """
void wrap_test_callback (void *instance) {
    boost::python::call<void> (reinterpret_cast<PyObject *> (instance));

static
void test_wrapper (PyObject *callback) {
    test (
        callback && (callback != Py_None)? wrap_test_callback: 0,
        callback);
}
"""

import os
from pyplusplus import \
    module_builder
from pygccxml.declarations.calldef import \
     argument_t
from pygccxml.declarations.cpptypes import \
    dummy_type_t, \
    pointer_t

# PyObject *
pyobject_type = pointer_t (dummy_type_t ("PyObject"))

mb = module_builder.module_builder_t( ["test.hpp"] )

test = mb.free_function (name = "test")
test.arguments = [ argument_t (name = "callback", type = pyobject_type)
]
test.name      = "test_wrapper"
test.rename ("test")

# this goes to the wrong source file :-(
mb.add_declaration_code (WRAPPER_CODE)

mb.build_code_creator( module_name='test_wrapper' )

mb.split_module( '.' )
--- 8>< ------ ><8 ---

Cheers,

Gottfried

Another problem with split_module

Ganssauge, Gottfried

Roman Yakovenko

Roman Yakovenko

Ganssauge, Gottfried

Roman Yakovenko

tags

participants (2)