From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 14CB158DF for ; Tue, 24 Jun 2014 00:24:53 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 23 Jun 2014 15:25:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,533,1400050800"; d="scan'208";a="532926159" Received: from fmsmsx107.amr.corp.intel.com ([10.19.9.54]) by orsmga001.jf.intel.com with ESMTP; 23 Jun 2014 15:25:01 -0700 Received: from fmsmsx117.amr.corp.intel.com (10.18.116.17) by FMSMSX107.amr.corp.intel.com (10.19.9.54) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 23 Jun 2014 15:25:00 -0700 Received: from fmsmsx105.amr.corp.intel.com ([169.254.5.225]) by fmsmsx117.amr.corp.intel.com ([169.254.3.56]) with mapi id 14.03.0123.003; Mon, 23 Jun 2014 15:25:01 -0700 From: "Rogers, Gerald" To: "Richardson, Bruce" , Stephen Hemminger , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Why rte_snprintf at all? Thread-Index: AQHPjwbzyDCNViwn7UecpW/YdOVFxZt/uXYA//+MagA= Date: Mon, 23 Jun 2014 22:25:00 +0000 Message-ID: References: <20140623101603.54a5d887@nehalam.linuxnetplumber.net> <59AF69C657FD0841A61C55336867B5B02CEE0C0E@IRSMSX103.ger.corp.intel.com> In-Reply-To: <59AF69C657FD0841A61C55336867B5B02CEE0C0E@IRSMSX103.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.2.140509 x-originating-ip: [10.34.81.205] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Why rte_snprintf at all? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 22:24:54 -0000 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@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? >>=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