[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Callback from C++ to Python Passing gr_message_sp

From: Jeremy Chew
Subject: Re: [Discuss-gnuradio] Callback from C++ to Python Passing gr_message_sptr
Date: Wed, 3 Jan 2007 21:39:31 +0800

It seems that gr_feval is called from Python and returns to Python, or is called from C and returns to C, if I'm not mistaken.

What I need to do is connect a pre-existing C++ MAC module with Python. Packets go in and out at the top and bottom of the MAC layer. Each packet does not go in and out of the MAC all within a single synchronous call. With the MAC working this way, how do we use gr_feval* without having the Python program poll the MAC?

----- Original Message ----- From: "Eric Blossom" <address@hidden>
To: "Jeremy Chew" <address@hidden>
Cc: <address@hidden>
Sent: Wednesday, January 03, 2007 4:57 PM
Subject: Re: [Discuss-gnuradio] Callback from C++ to Python Passing gr_message_sptr

On Wed, Jan 03, 2007 at 04:19:24PM +0800, Jeremy Chew wrote:

I'm working on a C++ extension.

How can we use SWIG to program a callback from C++ to Python that passes a
gr_message_sptr? I'm trying to avoid polling the C++ module from Python


Look at the code in gr_feval.{h,cc,i}, and the test code in qa_feval.py.
It currently supports callbacks from C++ to python using double,
complex, long and void. Passing a gr_message_sptr is completely analogous.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]