From: Luiz Fernando Capitulino <lcapitulino@conectiva.com.br>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: GCC-4 Patch for btsco
Date: Fri, 17 Jun 2005 15:49:27 -0300 [thread overview]
Message-ID: <42B31B37.30202@conectiva.com.br> (raw)
In-Reply-To: <42B31A2D.1020102@xmission.com>
Brad Midgley wrote:
> Guys,
>
> Should we just require bluez-libs 2.11 or use hci_switch_role
> conditionally? We seem to be very demanding :)
Require a library version is a common pratice, I don't see
any problem with that.
Pre-Processor conditional compile macros makes your code a bit
harder to understand and to mantain, it's not reasonable to
do that without a good reason.
Well, my 2 cents. :)
--
Luiz Fernando N. Capitulino
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-06-17 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 10:05 [Bluez-devel] GCC-4 Patch for btsco Bastien Nocera
2005-06-17 10:23 ` Marcel Holtmann
2005-06-17 10:51 ` [Bluez-devel] " Bastien Nocera
2005-06-17 11:05 ` Marcel Holtmann
2005-06-17 11:33 ` Bastien Nocera
2005-06-17 13:31 ` Brad Midgley
2005-06-17 20:11 ` Bastien Nocera
2005-06-17 20:49 ` Brad Midgley
2005-06-17 21:26 ` Bastien Nocera
2005-06-17 18:45 ` Brad Midgley
2005-06-17 18:49 ` Luiz Fernando Capitulino [this message]
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=42B31B37.30202@conectiva.com.br \
--to=lcapitulino@conectiva.com.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.