Re: [sc-dev] thisThread.clock or just clock in schedBundleArrayOnClock?

[Julian Rohrhuber <rohrhuber@xxxxxxxxxxxxxx>]

Ah this is a typo. I've fixed it - thanks for spotting it.

> I discovered this while researching the thread beats issue:
>
> 	schedBundleArrayOnClock { |clock, bundleArray, lag = 0, 
> server, latency|
> 		thisThread.clock.sched(this, {
> 					if (lag != 0) {
> 						SystemClock.sched(lag, {
>
> 	server.sendBundle(latency ? server.latency, *bundleArray)
> 						})
> 					} {
>
> 	server.sendBundle(latency ? server.latency, *bundleArray)
> 					}
> 		})
> 	}
>
> The method takes 'clock' as an argument, but the argument is never 
> used. Should we remove 'thisThread', or the argument?
>
> hjh
>
>
> : H. James Harkins
> : <mailto:jamshark70@xxxxxxxxxxxxxxxxx>jamshark70@xxxxxxxxxxxxxxxxx
> : <http://www.dewdrop-world.net>http://www.dewdrop-world.net
> .::!:.:.......:.::........:..!.::.::...:..:...:.:.:.:..:
>
> "Come said the Muse,
> Sing me a song no poet has yet chanted,
> Sing me the universal."  -- Whitman


--





.

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/