From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] HFP design question : polls opened !
Date: Tue, 09 Oct 2007 10:19:05 +0200 [thread overview]
Message-ID: <470B3979.4080301@free.fr> (raw)
In-Reply-To: <1191862220.12212.3.camel@aeonflux.holtmann.net>
Hi All,
>> To ease the pain we could use the brand new GRegex tool, that brings the
>> power of regular expressions to the glib world. That would meen however
>> that we would have to port it to eglib first.
>
> it is okay to depend on GLib for certain things. Starting with 4.x we
> will make GLib mandatory and remove eglib. However for the AT command
> parsing, I might wanna have a self written parser. This way it is more
> portable.
Marcel, there is no portability issue with GRegex : it is completely
self contained (no external deps added). ;-)
Cheers,
Fabien
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-09 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 15:46 [Bluez-devel] HFP design question : polls opened ! Fabien Chevalier
2007-10-08 16:50 ` Marcel Holtmann
2007-10-09 8:19 ` Fabien Chevalier [this message]
2007-10-09 8:45 ` Marcel Holtmann
2007-10-09 9:43 ` Fabien Chevalier
2007-10-09 10:02 ` Frédéric Dalleau
2007-10-09 10:10 ` Fabien Chevalier
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=470B3979.4080301@free.fr \
--to=fabchevalier@free.fr \
--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