On Wed, 2015-10-14 at 10:31 -0400, Rafael Schloming wrote:
> It wasn't actually an accidental commit. If I recall correctly I
> ended up
> using it more like a 0xDEADBEEF value. It makes it easy to
> distinguish
> between the failure mode of an actual hang (e.g. infinite loop or
> blocking
> call
It wasn't actually an accidental commit. If I recall correctly I ended up
using it more like a 0xDEADBEEF value. It makes it easy to distinguish
between the failure mode of an actual hang (e.g. infinite loop or blocking
call inside a handler) vs reaching a state where there are simply no more
On Mon, 2015-10-12 at 16:05 -0400, aconway wrote:
> ...
> +1, that looks like the right fix. 3141 is an odd choice of default,
> even for a mathematician.
>
At this point, I'm desperately trying to find an appropriate pi joke :
-)
Andrew
But it's obvious how this constant was chosen.
With circular reasoning.
- Original Message -
> On Mon, 2015-10-12 at 16:05 -0400, aconway wrote:
> > ...
> > +1, that looks like the right fix. 3141 is an odd choice of default,
> > even for a mathematician.
> >
>
> At this point,
On Sat, 2015-10-10 at 10:57 +0200, Bozo Dragojevic wrote:
> Hi Alan, Rafael,
>
> On 9. 10. 15 21.25, aconway wrote:
> > I'm fiddling with the C++ example broker, and when I install a
> > debug
> > handler, I see that when the broker is doing absolutely nothing
> > there
> > is a
Hi Alan, Rafael,
On 9. 10. 15 21.25, aconway wrote:
> I'm fiddling with the C++ example broker, and when I install a debug
> handler, I see that when the broker is doing absolutely nothing there
> is a PN_REACTOR_QUIESCED event about every 3 seconds. Does anybody know
> what this is about? Why is
