On Fri, Apr 26, 2019 at 09:41:00AM +, N. Benes wrote:
> So this seems to be a suitable pattern for my case.
Nicolas,
thanks for responding to your own email! It's a little thing, but it
keeps our archives complete, and if someone else runs into this issue,
it'll be useful for them.
-- M
si
N. Benes:
> what is the accepted best practice to have a source and a sink block
> share a common resource?
> In my case, the shared resource is a thread that does I/O and both
> source/sink use it to interface to GNU Radio.
[snip]
> Is there a commonly accepted pattern to apply in this situation
Hi GNU hackers,
what is the accepted best practice to have a source and a sink block
share a common resource?
In my case, the shared resource is a thread that does I/O and both
source/sink use it to interface to GNU Radio.
First I thought about adding the I/O thread to the source block and use
th
