From: "Simon Ruggier" <simon80@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] minor quibbles
Date: Sun, 24 Jun 2007 17:04:40 -0400 [thread overview]
Message-ID: <c1fa8edf0706241404y2471673cwf17b4e7aac86ef29@mail.gmail.com> (raw)
This doesn't seem like a big deal, but I noticed that there are a few
cases where a buffer[PATH_MAX + 1] is allocated, but then snprintf is
used with a size of up to PATH_MAX. The man page for snprintf on my
system says that "The functions snprintf() and vsnprintf() do not
write more than size bytes (including the trailing '\0').", which
would seem to imply that snprintf(buf, PATH_MAX + 1, ... ) is more
correct. Someone please correct me if I'm wrong about this.
I'm also wondering if it's intentional that certain hidd options, like
--no-check, are undocumented?
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2007-06-24 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c1fa8edf0706241404y2471673cwf17b4e7aac86ef29@mail.gmail.com \
--to=simon80@gmail.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