Re: [Live-devel] correct way to use TaskScheduler::unscheduleDelayedTask?

2016-08-26 Thread Ross Finlayson
> On Fri, Aug 26, 2016 at 12:07:45PM +0200, Ross Finlayson wrote: >> Yes, you are correct here. Fortunately, there is an easy fix (which I’ll >> add to the code in the near future): Set “fNext” to NULL at the start of the >> handler function (“sendNext()”). Ditto for the other places in the cod

Re: [Live-devel] correct way to use TaskScheduler::unscheduleDelayedTask?

2016-08-26 Thread Helmut Grohne
On Fri, Aug 26, 2016 at 12:07:45PM +0200, Ross Finlayson wrote: > Yes, you are correct here. Fortunately, there is an easy fix (which I’ll add > to the code in the near future): Set “fNext” to NULL at the start of the > handler function (“sendNext()”). Ditto for the other places in the code >

Re: [Live-devel] correct way to use TaskScheduler::unscheduleDelayedTask?

2016-08-26 Thread Ross Finlayson
> I caution that > updating the documentation is insufficient, because live555 does not > follow this rule itself. Yes, the “fNextTask” hack is problematic, and not just because of the example that you noted. It’s also a problem because it makes the (in general, unwarranted) assumption that the