On Mon, Jul 20, 2009 at 11:34 PM, troy d. straszheim wrote:
> I suppose this is a good time to follow up on this old post, advertising the
> std_map_indexing_suite that Jakob and I put together:
>
> http://article.gmane.org/gmane.comp.python.c%2B%2B/13642
>
> I'm wondering if the v2 interface sup
Roman Yakovenko wrote:
On Mon, Jul 20, 2009 at 8:51 PM, Matthew Scouten
(TT) wrote:
I would like to second this question.
Right now, I am, with help from other people and from the author
support this suite.
Here(
http://pygccxml.svn.sourceforge.net/viewvc/pygccxml/pyplusplus_dev/indexing_su
On Mon, Jul 20, 2009 at 8:51 PM, Matthew Scouten
(TT) wrote:
> I would like to second this question.
Right now, I am, with help from other people and from the author
support this suite.
Here(
http://pygccxml.svn.sourceforge.net/viewvc/pygccxml/pyplusplus_dev/indexing_suite_v2/
) you can find an
I would like to second this question.
Several times recently, I have needed to wrap STL-like containers that are
almost-vectors, just different enough that vector_indexing_suite does not work.
This is a minor PITA with the standard indexing_suite and looks like it will be
much easier with the n
Hi all,
I'm extending C++ with Boost.Python.
At some point I need to call a Python function on an object of unknown
Python type.
I found those 2 solutions, but they seem so simple that they make me wonder
about the dangerosity of doing this (I'm a newbie to Boost.Python):
static void test_func_a
