From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] Why rte_snprintf at all?
Date: Mon, 23 Jun 2014 10:16:03 -0700 [thread overview]
Message-ID: <20140623101603.54a5d887@nehalam.linuxnetplumber.net> (raw)
Why does rte_snprintf exist? It seems like a misunderstanding or broken
implementation of snprintf in some other C library. For standard Glibc,
I get same result from rte_snprintf and snprintf for all inputs including
boundary cases
next reply other threads:[~2014-06-23 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 17:16 Stephen Hemminger [this message]
2014-06-23 22:18 ` Richardson, Bruce
2014-06-23 22:25 ` Rogers, Gerald
2014-06-23 22:31 ` Wiles, Roger Keith
2014-06-23 22:34 ` Richardson, Bruce
2014-06-23 22:46 ` Wiles, Roger Keith
2014-06-23 22:53 ` Richardson, Bruce
2014-06-24 9:22 ` Thomas Monjalon
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=20140623101603.54a5d887@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).