On Tue, Jun 16, 2015 at 10:16 AM, Nick Foster <bistrom...@gmail.com> wrote:
> Issue #1 is likely the problem. Thanks for pointing that out, Andy! The > other two issues should be pretty miniscule in overhead, but are probably > good ideas nonetheless. The block was written for clarity rather than for > speed, but even so it shouldn't be particularly heavy-duty. > In the future, we plan to allow designating a non-empty message queue as a prior condition to be satisfied before the scheduler calls work(), thus it will won't ever be necessary to block inside work directly on the queue itself. This is a common issue with source blocks that rely on input message ports for content. -- Johnathan Corgan Corgan Labs - SDR Training and Development Services Intro to SDR Class - June 29-30, El Segundo, CA http://corganlabs.com
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
