> 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() This is maybe acceptable, but I think it is more important to keep a const in the API, explicitly saying to the API user that this parameter is read only. Olivier
