>Hi Sean, Tom and Martin,
>basic_block enforces using a symbol in its message_port_register_in method, so
>that's where you'd have to start changing things.
>But to add my 0b0010* ct to this:
>- using strings as port names keeps consistency
>- using strings is the "proper" way to ensure all too
Hi Sean, Tom and Martin,
basic_block enforces using a symbol in its message_port_register_in method, so
that's where you'd have to start changing things.
But to add my 0b0010* ct to this:
- using strings as port names keeps consistency
- using strings is the "proper" way to ensure all tools (es
On 02/28/2014 01:39 AM, Nowlan, Sean wrote:
>> Hey Sean,
>
>> I /think/ so. I'd have to double check, but at some point it's
>> likely to go through a symbol_to_string conversion.
>
>> Can you think of a need for a port name to be something other than
>> a symbol/string? Maybe an enumeration or s
>
>From: trond...@trondeau.com [trond...@trondeau.com] on behalf of Tom Rondeau
>[t...@trondeau.com]
>Sent: Thursday, February 27, 2014 2:45 PM
>To: Nowlan, Sean
>Cc: discuss-gnuradio@gnu.org
>Subject: Re: [Discuss-gnuradio] messag
On Mon, Feb 24, 2014 at 2:46 PM, Nowlan, Sean
wrote:
> Quick question: can a message port name be any valid PMT type? Or does it
> have to be a string converted to a symbol?
>
> Thanks,
>
> Sean
Hey Sean,
I /think/ so. I'd have to double check, but at some point it's likely
to go through a symbo
Quick question: can a message port name be any valid PMT type? Or does it have
to be a string converted to a symbol?
Thanks,
Sean
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
