From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rogers, Gerald" Subject: Re: Why rte_snprintf at all? Date: Mon, 23 Jun 2014 22:25:00 +0000 Message-ID: References: <20140623101603.54a5d887@nehalam.linuxnetplumber.net> <59AF69C657FD0841A61C55336867B5B02CEE0C0E@IRSMSX103.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: "Richardson, Bruce" , Stephen Hemminger , "dev-VfR2kkLFssw@public.gmane.org" Return-path: In-Reply-To: <59AF69C657FD0841A61C55336867B5B02CEE0C0E-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org> Content-Language: en-US Content-ID: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" Bruce, Stephen, It may be a duplicate, but people are likely using it. I would assume deprecate means don=B9t remove, but put in a comment that says please don= =B9t use and migrate your code away from it. Thanks, Gerald On 6/23/14, 3:18 PM, "Richardson, Bruce" 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? >>=20 >> 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