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

PrevNext  Index
DateSun, 03 Jun 2012 19:16:09 +0300
From Nedko Arnaudov <[hidden] at arnaudov dot name>
ToFlorian Paul Schmidt <[hidden] at gmx dot net>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToFlorian Paul Schmidt Re: [Jack-Devel] [LAU] jack2 turned verbose
Follow-UpFlorian Paul Schmidt Re: [Jack-Devel] [LAU] jack2 turned verbose
Florian Paul Schmidt <[hidden]> writes:

> On 06/01/2012 09:54 PM, Nedko Arnaudov wrote:
>>
>> Nedko, does your advice to use -O0 only concern Jack or everything?
>> I'm compiling lots of software here, usually -O2 usually doesn't seem
>> to cause problems.
>> YMMV. Default compiler in my distro (Gentoo) works properly. jack also
>> "works", until you find that it misbehaves. You can only be sure if you
>> have tests that cover 100% of the code. Neither jack1 nor jack2 have
>> such.
>>
>>
>
> 100% code coverage in tests does not guarantee all bugs are found. You
> also need to test 100% of all possible input/output pairs.. Example: I
> have a function that calculates some mathematical function and has a
> conditional branch somewhere in it. Now I write two tests (one
> input/output pair each to compare against) to cover both cases of the
> conditional. Does that guarantee to me that the code works for ALL
> inputs? No, not at all. Only reasoning (a.k.a. a proof) will give you
> that...

Yes, 100% code coverage is not enough but is still required.

So users shall do what? Hope and pray? Or play a prey? Whats the
direction? Are there any automated tests? Or we use users as guinea
pigs? Is this how free software is supposed to work?

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
PrevNext  Index

1338740189.25841_0.ltw:2,a <87ipf8gyly.fsf at arnaudov dot name>