Re: (Re: Beast Jack driver)

i'm taking Paul off the Cc: list, since we're probably just pestering
with most stuff. Paul, FYI this is also all available through gmane:
or of course our list archives:

On Tue, 6 Jun 2006, Stefan Westerfeld wrote:

On Mon, Jun 05, 2006 at 04:31:23AM +0200, Tim Janik wrote:

DEBUG ("attaching to JACK server returned status: %d\n", status);
/* FIXME: check status for proper error reporting

doesn't teh jack API have something like:
 const char* jack_status_to_string (jack_status_t status);


fine, then we need to roll our own function that does this.
for existing example code that stringifies foreign errors,
you can take a look at gslvorbis-cutter.c:ov_error_blurb().

it might be agood idea to submit this to jack once done btw.

Its not that writing our own function will help us a lot though. Its not
that every function returns a jack_status_t. Just the open function.

it will help to improve the debugging output. we've done that for all
other drivers, we should also do it here. and it prolly wouldn't hurt
JACK to export status stringification.

The usual way for getting stringified errors in other situations is to
set the error callback with jack_set_error_function.

dunno how that's applicable here...

  Cu... Stefan


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]