Whats the difference between using tb.start() + tb.wait() Vs tb.run()
Vs
tb.stop + tb.wait()
All the three are giving me the same result for the following code
*tb.start() + tb.wait() *
if __name__ == '__main__':
tb = rx_cfile_block1(2450000000,'/home/sumit/first_app_data1')
tb.start()
tb.wait()
sleep(5)
tb = rx_cfile_block1(2460000000,'/home/sumit/first_app_data2')
tb.start()
tb.wait()
*tb.run()*
if __name__ == '__main__':
tb = rx_cfile_block1(2450000000,'/home/sumit/first_app_data1')
tb.run()
sleep(5)
tb = rx_cfile_block1(2460000000,'/home/sumit/first_app_data2')
tb.run()
*tb.stop + tb.wait()*
if __name__ == '__main__':
tb = rx_cfile_block1(2450000000,'/home/sumit/first_app_data1')
tb.stop()
tb.wait()
sleep(5)
tb = rx_cfile_block1(2460000000,'/home/sumit/first_app_data2')
tb.stop()
tb.wait()
--
View this message in context:
http://gnuradio.4.n7.nabble.com/Reg-start-wait-sto...
Sent from the GnuRadio mailing list archive at Nabble.com.
on 2012-10-09 01:15
on 2012-10-09 01:28
On 10/08/2012 04:14 PM, sumitstop wrote: > tb.wait() > sleep(5) > tb = rx_cfile_block1(2460000000,'/home/sumit/first_app_data2') > tb.run() > run = start() + wait() > > Essentially nothing should happen, threads are interrupted and joined. Since there are no threads, both calls should return immediately. -josh
on 2012-10-09 01:36
Thanks Josh .. got it .. that last one stop() + wait() I forgot to check by myself before posting .. sorry for that -- View this message in context: http://gnuradio.4.n7.nabble.com/Reg-start-wait-sto... Sent from the GnuRadio mailing list archive at Nabble.com.
Please log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.