Excerpts from Kai Vehmanen's message of 2010-09-04 13:26:04 +0200:
> Hi,
>
> On Sat, 17 Jul 2010, Philipp wrote:
>
> > jack_client_new() is deprecated since quite a long time. Use
> > jack_client_open() instead:
> > http://jackaudio.org/files/docs/html/group__ClientFunctions.html#ga28977ad0cccf08cd600dd220e2b1c880>
> this is now fixed in ecasound's git tree and will be in the next release.
>
> I did not change to jack_client_open() immediately as I didn't want
> to force people to update their JACK version (e.g. Debian provided a very
> old JACK for a long time) for this reason alone. But of course,
> jack_client_new() was deprecated in 2004, so it's about time for really
> stop using it in ecasound as well. Apologies to everyone still using a
> pre-2004 JACK in their systems! ;)

Thanks. Yep, I also think it's about time ;)
There were a few new jack versions and deprecations in the meanwhile :)

Ok. It's hard for me to know where a bug comes from, so I keep reporting
:)
Even with my little piece of software I noticed that stuff behaves
different than I expected.

This was especially the case with my little reconnect thingy. I didn't
know jack client/port names with spaces aren't allowed, so it didn't
work with those. Escaping spaces was fun too, '' or "" works with
jack_connect but only \ works with ecasounds jack-connect. I ran into
another unexpected behavior when trying to avoid parsing the connections
when unnecessary. There I found that in some cases jack_lsp returns a
different order of connections for the same graph, consequently a
different string and thus breaking my optimization. It seems like
software is full of unexpected behavior :)