Re: [Discuss-gnuradio] Problem with my modified IP tunnelling example

[Jeremy Chew]

Thanks again. This information really helps.

This may sound like a silly question: If the packets are SWIG-wrapped, am I 
right that this means I need to use SWIG to handle them in the C++ 
extension? This is an important question to me as I am not familiar with 
SWIG.

Jeremy

----- Original Message ----- 
From: "Eric Blossom" <address@hidden>
To: "Jeremy Chew" <address@hidden>
Cc: <address@hidden>; "Harry Han" <address@hidden>
Sent: Tuesday, December 05, 2006 12:22 PM
Subject: Re: [Discuss-gnuradio] Problem with my modified IP tunnelling 
example


> On Tue, Dec 05, 2006 at 11:06:04AM +0800, Jeremy Chew wrote:
> > Thanks Eric.
> >
> > Regarding the packet data-type, since I'm modifying
> > gnuradio-examples-0.7/python/gmsk2/tunnel_ip_null_mac.py, I want to have
> > the same format used
> > in that file. Based on examination of the Python code used in there, I
> > understand that the packets are Python strings.
> >
> > Could I confirm that this is true? I'm afraid that a wrong packet 
> > data-type
> > is
> > causing the crash when the callback is called.
> >
> > Jeremy
>
> It's a SWIG wrapped C++ gr_message_sptr.  It is not a string.
>
> address@hidden ~]$ python
> Python 2.4.2 (#1, Oct 13 2006, 17:11:24)
> [GCC 4.1.0 (SUSE Linux)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> > > > from gnuradio import gr
> > > > m=gr.message()
> > > > m
> <gnuradio.gr.gnuradio_swig_python.gr_message_sptr; proxy of <Swig Object 
> of type 'gr_message_sptr *' at 0x80c44b8> >
> > > > type(m)
> <class 'gnuradio.gr.gnuradio_swig_python.gr_message_sptr'>
> > > >