From: Marcel Holtmann <marcel@holtmann.org>
To: "Williams, Richard" <Richard.Williams@VITRONICS.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Problem with read on RFCOMM Sockets
Date: Wed, 16 Jun 2004 15:27:33 +0200 [thread overview]
Message-ID: <1087392453.4309.19.camel@pegasus> (raw)
In-Reply-To: <A1F0D47583A2D711919F00600819B3A45BDC12@goofy.vitronics.com>
Hi Richard,
> I understand why strlen should not be used in this case, but why
> unsigned char instead of char ? There are many examples of the
> use of the generic file I/O read() function in the literature
> using char buffers. Is this case different ?
it actually depends on the other side. If the other side also uses char
then there should be no problem, but it is better to use unsigned char
if you don't know what the other side is sending.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-16 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 13:17 [Bluez-devel] Problem with read on RFCOMM Sockets Williams, Richard
2004-06-16 13:27 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-15 18:31 ionut dediu
2004-06-15 22:49 ` Marcel Holtmann
2004-06-16 11:11 ` ionut dediu
2004-06-16 11:32 ` 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=1087392453.4309.19.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Richard.Williams@VITRONICS.com \
--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