From: "Thomas Lußnig" <bluez@suche.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BT-Sco
Date: Fri, 26 Nov 2004 17:33:01 +0100 [thread overview]
Message-ID: <41A75ABD.2050605@suche.org> (raw)
In-Reply-To: <1101481147.6514.10.camel@pegasus>
>the source code size of this version is amazing, but the coding style is
>crap. Sorry to say that.
>
>
For the current version the size is to large but i thought of extending
the source to allow multiple Headsets.
Than it does not grow much since it already use an record and no static
variables.
>Don't use {{{ and include some newlines. Actually follow the kernel
>coding style.
>
>
The {{{ i use for folding marks they can be replaced with { same as with
}}} and }.
>Why do you rewrite the function from libbluetooth and libasound. Simply
>use them, because these are shared library and they are loaded anyway.
>
>
1. What function of libbluetooth ? The only bluetooth function in wich
would be useable is geting
the local mac and the remove channel and string2adress conversion. wich
is in no relation to the
size the binary would grow. With the same ground you could ask why i
rewrite the asound part.
Here the ground is even more interesting.
1. I save many file open / close
2. It run faster
3. If the sound device support async io or even only signaling if there
are new mixer data it can be done without
poll.
The ground i rewrite the original was so that i can use these code more
easy to add it so other programms like kphone
and use the button with switch sco on/off for accepting phone calls.
Cu Thomas
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-11-26 16:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 18:12 [Bluez-devel] audio problems with a2play Brad Midgley
2004-11-22 18:39 ` Marcel Holtmann
2004-11-22 18:50 ` Brad Midgley
2004-11-23 2:34 ` Henryk Plötz
2004-11-23 3:49 ` Brad Midgley
2004-11-23 5:34 ` Marcel Holtmann
2004-11-23 6:06 ` Henryk Plötz
2004-11-23 9:34 ` Marcel Holtmann
2004-11-23 19:41 ` Henryk Plötz
2004-11-23 14:20 ` Brad Midgley
2004-11-23 19:38 ` Henryk Plötz
2004-11-23 21:14 ` Marcel Holtmann
2004-11-24 2:47 ` Henryk Plötz
2004-11-24 5:24 ` Marcel Holtmann
2004-11-23 21:34 ` Brad Midgley
2004-11-23 21:52 ` Marcel Holtmann
2004-11-24 3:16 ` Brad Midgley
2004-11-24 5:09 ` Marcel Holtmann
2004-11-25 5:08 ` Henryk Plötz
2004-11-24 2:58 ` Henryk Plötz
2004-11-24 4:22 ` Brad Midgley
2004-11-24 4:54 ` Brad Midgley
2004-11-24 5:06 ` Marcel Holtmann
2004-11-26 15:46 ` [Bluez-devel] BT-Sco Thomas Lußnig
2004-11-26 14:59 ` Marcel Holtmann
2004-11-26 16:33 ` Thomas Lußnig [this message]
2004-11-26 17:19 ` Marcel Holtmann
2004-11-28 3:07 ` Brad Midgley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41A75ABD.2050605@suche.org \
--to=bluez@suche.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox