DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Rogers, Gerald" <gerald.rogers@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Why rte_snprintf at all?
Date: Mon, 23 Jun 2014 22:25:00 +0000
Message-ID: <CFCDF705.57A9D%gerald.rogers@intel.com> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B02CEE0C0E@IRSMSX103.ger.corp.intel.com>

Bruce, Stephen,

It may be a duplicate, but people are likely using it.  I would assume
deprecate means don¹t remove, but put in a comment that says please don¹t
use and migrate your code away from it.



On 6/23/14, 3:18 PM, "Richardson, Bruce" <bruce.richardson@intel.com>

>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger
>> Sent: Monday, June 23, 2014 10:16 AM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] Why rte_snprintf at all?
>> 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
>> boundary cases
>It can indeed probably be deprecated in next release. Any objections?

  reply	other threads:[~2014-06-23 22:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 17:16 Stephen Hemminger
2014-06-23 22:18 ` Richardson, Bruce
2014-06-23 22:25   ` Rogers, Gerald [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CFCDF705.57A9D%gerald.rogers@intel.com \
    --to=gerald.rogers@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git