Re: [Jack-Devel] The Situation(s) With JACK

PrevNext  Index
DateWed, 14 Dec 2011 15:02:19 +0100
From Stéphane Letz <[hidden] at grame dot fr>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToPaul Davis Re: [Jack-Devel] The Situation(s) With JACK
Follow-UpPaul Davis Re: [Jack-Devel] The Situation(s) With JACK
Follow-UpFelix Homann Re: [Jack-Devel] The Situation(s) With JACK
Follow-UpMark Constable Re: [Jack-Devel] The Situation(s) With JACK
Le 14 déc. 2011 à 14:55, Paul Davis a écrit :

> On Wed, Dec 14, 2011 at 5:25 AM, Stéphane Letz <[hidden]> wrote:
> 
>>> 
>>> Anyway modern C++ gets my ++.
>>> Watching the threads, thanks. Tim.
>>> 
>> 
>> And one way to improve the situation is to make a clear choice or the reference code base.
> 
> i don't think that *anyone* believes that the C code base of JACK1 is
> an appropriate thing to keep developing. certainly I do not. even
> though its actually easier to add a new callback to JACK1 than to
> JACK2, its completely obvious that the JACK1 codebase is dead as a
> future/longterm development path.
> 
> the question is not "do we we keep working on the JACK1 C code base or
> the JACK2 C++ code base?"
> 
> the questions is: (given that) we (active JACK developers all)
> want/need a C++ implementation. is the JACK2 codebase the right
> starting point for that, or do we gain something by doing a new
> implementation that draws from JACK2 but leverages boost (among other
> things) and uses fully idiomatic C++ unless doing so compromises
> performance notably.

OK, assuming the answer to "do we gain something by doing a new implementation" is yes, the next question is : who is going todo that? who is going to do multi-OS support? who is going to port current specific code (backend, bridges?) to this now code base? who is going to debug/test it?

Stephane 
PrevNext  Index

1323871567.15462_0.ltw:2,a <DC307597-5BA4-436A-9388-184D33273382 at grame dot fr>