[Jack-Devel] how you can love JACK back

PrevNext  Index
DateMon, 04 Jun 2012 10:25:41 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToJACK <[hidden] at lists dot jackaudio dot org>
Follow-UpAdrian Knoth [FFADO-devel] Fwd: [Jack-Devel] how you can love JACK back
Follow-UpRobin Gareus Re: [Jack-Devel] how you can love JACK back
Follow-UpHarry van Haaren Re: [Jack-Devel] how you can love JACK back
its fairly clear that neither myself nor stephane are going to find the
time on any foreseeable timeline to do the complete review+merge of the
JACK headers that has been proposed to ease *some* of the issues
surrounding future JACK development.

however, that doesn't mean that it can't happen. i know that i can review
material far faster if its in the "right" format. my guess that the same is
true for stephane as well.

so here is a proposal/request for help from the JACK community to ensure
that this gets done. you don't need to be a coder (though you do need to be
able to read code).

what we need is a breakout of all the functions defined in the header files
that get installed by jack1 and jack2. the result should be, preferably, a
side-by-side (literally) juxtaposition of the comments/docs for each
function, and the declaration of the function. This is mostly a text
editing task, in fact, with a need for good presentation. The result should
be something that is easy to go through and review the differences. In a
few cases, there will be a function that exists in only one version.

remember: you don't need to be any kind of uber-coder, or even a coder at
all, to help with this incredibly valuable task. you just need to be able
read header files, find stuff in two parallel (and different) trees of
header files, and collate what you find into some format that we can easily
review.

please step up :)

--p
PrevNext  Index

1338819956.19350_0.ltw:2,a <CAFa_cKnDe0PA8VB4Ae9FjaCdMxW66Xo8hXnVZ3A5j9O3ACc0fw at mail dot gmail dot com>