Re: [Jack-Devel] how you can love JACK back

PrevNext  Index
DateMon, 04 Jun 2012 12:16:21 -0400
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToHarry van Haaren <[hidden] at gmail dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToHarry van Haaren Re: [Jack-Devel] how you can love JACK back
Follow-UpHarry van Haaren Re: [Jack-Devel] how you can love JACK back
Follow-UpRobin Gareus Re: [Jack-Devel] how you can love JACK back
On Mon, Jun 4, 2012 at 12:14 PM, Harry van Haaren <[hidden]>wrote:

> Hi all,
>
> I'm willing to contribute some time to this. I've pulled code a la Robin's
> suggestion, and have "Meld" doing the dirty work: it compares similar files
> and graphically shows the changes.
>
> I've a little situation: what if the documentation is different for a
> function?
>
> Eg Jack1:
> /* <b>THIS FUNCTION IS DEPRECATED AND SHOULD NOT BE USED IN
>  *  NEW JACK CLIENTS</b>
> */
>
> Jack2:
> /* \bold THIS FUNCTION IS DEPRECATED AND SHOULD NOT BE USED IN
> *  NEW JACK CLIENTS
> *
> * @deprecated Please use jack_client_open().
> */
>
> I'm not very familiar with doxygen tags etc, but it seems nice to tag the
> function as deprecated and point to _open?
>
> Do we edit the JACK1 file, or how do we want to merge these?
>

the initial goal is to be *able* to ask these qestions.

once we can ask them easily and across the entire API, the next goal is to
actually *ask* them :)
PrevNext  Index

1338826600.23734_0.ltw:2,a <CAFa_cKnE_61kuWm+MXJo7Dk8Cr3c0jVx2zHoyPeuC=ccoM9Ukg at mail dot gmail dot com>