Re: [Jack-Devel] [LAU] jack2 turned verbose

PrevNext  Index
DateSat, 02 Jun 2012 17:23:01 +0000
From Fons Adriaensen <[hidden] at linuxaudio dot org>
ToNedko Arnaudov <[hidden] at arnaudov dot name>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToNedko Arnaudov Re: [Jack-Devel] [LAU] jack2 turned verbose
Follow-UpNedko Arnaudov Re: [Jack-Devel] [LAU] jack2 turned verbose
On Sat, Jun 02, 2012 at 07:09:24PM +0300, Nedko Arnaudov wrote:

> Fons Adriaensen <[hidden]> writes:
> 
> > What this tells me is that one should test booleans against
> > boolean constants, and ints against int constants, and *not*
> > mix them up. Which I guess the libdbus code is doing.
 
> This guesswork fails. libdbus doesnt do this if only because it uses
> dbus_bool_t and not C99 nor C++ bool.

It some software implements its own boolean type, and then in
some cases decides that a given value of that type is neither
true nor false - as you wrote in a previous post - then that
is a bug. The essence of a boolean is that it always either
true or false. My suspicion is based on what you wrote, nothing
else.

> OTOH this is quickly becomming offtopic and dbus-fud-y.

Showing that the compiler does the right thing with booleans
(which is what my simple example code does) is not offtopic
in this context. And formulating a working hypothesis based
on that and previous evidence (see above) is not FUD.

Ciao,

-- 
FA

A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
PrevNext  Index

1338657788.22317_0.ltw:2,a <20120602172300.GF18406 at linuxaudio dot org>