From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: Date: Sun, 24 Jun 2007 17:04:40 -0400 From: "Simon Ruggier" To: "BlueZ development" MIME-Version: 1.0 Subject: [Bluez-devel] minor quibbles Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net 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