Re: [Jack-Devel] jack1 version jack2 public headers comparison

PrevNext  Index
DateTue, 28 Feb 2012 09:39:12 -0500
From Paul Davis <[hidden] at linuxaudiosystems dot com>
ToNedko Arnaudov <[hidden] at arnaudov dot name>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToNedko Arnaudov Re: [Jack-Devel] jack1 version jack2 public headers comparison
Follow-UpNedko Arnaudov Re: [Jack-Devel] jack1 version jack2 public headers comparison
On Tue, Feb 28, 2012 at 9:26 AM, Nedko Arnaudov <[hidden]> wrote:

> jack_get_version_string() is also required for reporting jack server
> version over dbus. I want this information to be present somewhere in
> gladish (the GUI frontend bundled in the ladish tarball).

this just defers the question: what is the purpose of presenting
anyone with this version number?

> As for the first function I'm all for feature based tests but we
> dont really have this in the API yet. jackdbus doesnt use nor exports
> the major/minor/micro/proto data over dbus. At least not yet.

i don't mean an API to test for features. i am talking about weak
linkage, primarily. i continue to see no reason to make the JACK
version available. it just promotes bad coding.

>>> jack_port_type_id_t jack_port_type_id (const jack_port_t *port) JACK_OPTIONAL_WEAK_EXPORT;
>>
>> needed for?
>>
>>> typedef uint32_t jack_port_type_id_t;
>>
>> use?
>
> jackdbus uses it to report [integer] port types over dbus.

why integer and not string as within the JACK API itself?
PrevNext  Index

1330439967.891_0.ltw:2,a <CAFa_cKm6TR0o91CPKf+vhX05prLWRoBpCir_S4Goj5L+n6j5FQ at mail dot gmail dot com>