From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] btohs,btohl, ...
Date: Wed, 09 Feb 2005 14:19:31 +0100 [thread overview]
Message-ID: <1107955171.13863.26.camel@pegasus> (raw)
In-Reply-To: <20050209140701.2cf50710@CleverSophie>
Hi Bjoern,
if you sign emails that go to a mailing list. Make sure that your key is
available on a public keyserver. Yours is not.
> I implemented a client server over bluetooth and I was wondering if I need the Little Endian, Big Endien conversion functions btohs,btohl,htobs,htobl?
if both sides are of the same endianess then not, but it is a good
programming style to always use them.
> Do I need to convert every single byte? which is received or sent over my sock_stream socket?
> If yes, should it look like this for the receiving case: btohs(buf[0]).... an so on for every byte?
For what do you wanna swap a byte and with what? There is nothing to
swap. Think about it ;)
Regards
Marcel
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-09 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 13:07 [Bluez-devel] btohs,btohl, # Björn Specht #
2005-02-09 13:19 ` Marcel Holtmann [this message]
2005-02-09 13:38 ` # Björn Specht #
2005-02-09 13:57 ` Marcel Holtmann
2005-02-09 14:00 ` # Björn Specht #
2005-02-09 15:07 ` [Bluez-devel] omtu, imtu # Björn Specht #
2005-02-09 15:18 ` Marcel Holtmann
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=1107955171.13863.26.camel@pegasus \
--to=marcel@holtmann.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 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.