[Firebird-devel] isc_que_events immediate callback

2016-01-04 Thread Geoff Worboys
Hi, I am trying to understand isc_que_events and hoping someone here can help me. :-) I'm still on Firebird v2.5.4 but there's nothing in the changelog to suggest any differences to the following... If I call isc_event_block to allocate the buffers, and pass those to isc_que_events I get an imm

Re: [Firebird-devel] isc_que_events immediate callback

2016-01-04 Thread Dimitry Sibiryakov
04.01.2016 14:34, Geoff Worboys wrote: > I thought that maybe it might be important to grab the current > counter values with that first call to isc_que_events, but that > doesn't make any sense, as it appears that the returned counter > is always an increment of the passed in existing counter rath

Re: [Firebird-devel] isc_que_events immediate callback

2016-01-04 Thread Geoff Worboys
Dimitry Sibiryakov wrote: > 04.01.2016 14:34, Geoff Worboys wrote: >> I thought that maybe it might be important to grab the current >> counter values with that first call to isc_que_events, but that >> doesn't make any sense, as it appears that the returned counter >> is always an increment of the

Re: [Firebird-devel] isc_que_events immediate callback

2016-01-04 Thread Dimitry Sibiryakov
04.01.2016 15:49, Geoff Worboys wrote: > Which leaves me trying to work out how to determine whether I can > ignore a callback or not. Is there a reliable way to do this so > that I don't signal an event when there hasn't actually been one? I use following code: isc_event_block(...); isc_wait

Re: [Firebird-devel] isc_que_events immediate callback

2016-01-04 Thread Geoff Worboys
Dimitry Sibiryakov wrote: > 04.01.2016 15:49, Geoff Worboys wrote: >> Which leaves me trying to work out how to determine whether I can >> ignore a callback or not. Is there a reliable way to do this so >> that I don't signal an event when there hasn't actually been one? >I use following code