Hi all,

Does anyone know if the scheduler is guaranteed to process blocks in
the correct order?  For example, say you have a block with side
effects such as writing to a file, could it ever occur that the
scheduler is processing several work functions for the same block
concurrently in different threads,  the threads execute at a different
rate and you end up with a file written out of order?  In a similar
manner is accessing block member variables safe?  For example I want
to write a 'latch' block that takes in and outputs bits.  The output
will be low while the input is low until the first high bit is
received and then the output will remain high until it is reset.  If I
store the latch state in a member variable is it guaranteed that when
the latch is triggered at a given sample number all the output sample
before hand will be 0 and all after will be 1?

Many thanks,

Ben Gear


_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to