From: milosz danielewski <master@apnet.pl>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] sdp_uuid32_to_uuid128, lack of declaration
Date: Mon, 5 Mar 2007 19:14:47 +0000 (UTC) [thread overview]
Message-ID: <loom.20070305T200231-670@post.gmane.org> (raw)
In-Reply-To: 1173029470.5752.6.camel@aeonflux.holtmann.net
Marcel Holtmann <marcel <at> holtmann.org> writes:
>
> Hi Milosz,
>
> > Why there are no sdp_uuid32_to_uuid128 declaration in sdp_lib.h
> > (bluez-libs-devel 3.7.1)? It would be useful, but in such situation I
> > cannot use it...
>
> I think that is simply because nobody needed them before. Feel free to
> implement them and send a patch.
As far, as I can see it's already implemented, just not exposed in header file.
> However UUID32 is the most unused UUID
> type. In general you should either use UUID16 for well known profile and
> service identifiers or UUID128 for your own identifiers.
I've started to implement jsr82. When I create java object representing UUID
it's most convenient to pass 16 byte array from native C to Java. So, when I
iterate over service attributes, have to properly convert SDP_UUID32 to uuid128.
That's why I need to use sdp_uuid32_to_uuid128 (which is already implemented and
working). Only problem is ugly warning "implicit declaration".
milosz danielewski
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-03-05 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 11:20 [Bluez-devel] sdp_uuid32_to_uuid128, lack of declaration milosz danielewski
2007-03-04 17:31 ` Marcel Holtmann
2007-03-05 19:14 ` milosz danielewski [this message]
2007-03-05 20:22 ` Marcel Holtmann
2007-03-05 19:44 ` milosz danielewski
2007-03-05 20:50 ` Marcel Holtmann
2007-03-05 20:50 ` milosz danielewski
2007-03-05 21:55 ` Marcel Holtmann
2007-03-04 20:47 ` Albert Huang
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=loom.20070305T200231-670@post.gmane.org \
--to=master@apnet.pl \
--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