From: "Rogers, Gerald" <gerald.rogers-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "Richardson,
Bruce" <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Stephen Hemminger
<stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>,
"dev-VfR2kkLFssw@public.gmane.org"
<dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: Why rte_snprintf at all?
Date: Mon, 23 Jun 2014 22:25:00 +0000 [thread overview]
Message-ID: <CFCDF705.57A9D%gerald.rogers@intel.com> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B02CEE0C0E-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
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.
Thanks,
Gerald
On 6/23/14, 3:18 PM, "Richardson, Bruce" <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
wrote:
>> -----Original Message-----
>> From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of Stephen Hemminger
>> Sent: Monday, June 23, 2014 10:16 AM
>> To: dev-VfR2kkLFssw@public.gmane.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
>>including
>> boundary cases
>
>It can indeed probably be deprecated in next release. Any objections?
>
>/Bruce
next prev parent reply other threads:[~2014-06-23 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 17:16 Why rte_snprintf at all? Stephen Hemminger
[not found] ` <20140623101603.54a5d887-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-06-23 22:18 ` Richardson, Bruce
[not found] ` <59AF69C657FD0841A61C55336867B5B02CEE0C0E-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-23 22:25 ` Rogers, Gerald [this message]
[not found] ` <CFCDF705.57A9D%gerald.rogers-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-06-23 22:31 ` Wiles, Roger Keith
[not found] ` <AA49F83C-6C0A-45DD-B3D4-5D12BCFA9D49-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2014-06-23 22:34 ` Richardson, Bruce
[not found] ` <59AF69C657FD0841A61C55336867B5B02CEE1C3A-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-23 22:46 ` Wiles, Roger Keith
[not found] ` <E84A4CA4-9026-43E8-81B0-D17EAD1E64E4-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2014-06-23 22:53 ` Richardson, Bruce
[not found] ` <59AF69C657FD0841A61C55336867B5B02CEE1C5C-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
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=CFCDF705.57A9D%gerald.rogers@intel.com \
--to=gerald.rogers-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.