From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [RFC 10/35] eal: introduce RTE_DECONST macro Date: Fri, 11 Mar 2016 13:47:33 -0800 Message-ID: <20160311134733.7b931eec@xeon-e3> References: <1457540381-20274-1-git-send-email-olivier.matz@6wind.com> <1457540381-20274-11-git-send-email-olivier.matz@6wind.com> <56E08BE7.6030906@6wind.com> <20160309130159.309e5606@xeon-e3> <56E12C48.3070107@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" To: Olivier MATZ Return-path: Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by dpdk.org (Postfix) with ESMTP id E2A772BF1 for ; Fri, 11 Mar 2016 22:47:21 +0100 (CET) Received: by mail-pa0-f51.google.com with SMTP id fe3so92904738pab.1 for ; Fri, 11 Mar 2016 13:47:21 -0800 (PST) In-Reply-To: <56E12C48.3070107@6wind.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, 10 Mar 2016 09:11:52 +0100 Olivier MATZ wrote: > > > I would rather have the mempool_audit code take a non-const argument. > > The macro method sets a bad precedent and will encourage more bad code. > > Plus code checkers are likely to flag any such usage as suspect. > > Doing that would imply dropping the const qualifier in several > functions: > > - rte_mempool_dump() > - rte_mempool_audit() > - mempool_audit_cookies() > - mempool_audit_cache() Sure no problem.