On Wed, Sep 20, 2023 at 03:13:40PM +0200, Thomas Haller wrote: [...] > There are many places that rightly cast away const during free. But not > all of them. Add a free_const() macro, which is like free(), but accepts > const pointers. We should always make an intentional choice whether to > use free() or free_const(). Having a free_const() macro makes this very > common choice clearer, instead of adding a (void*) cast at many places. I wonder whether pointers to allocated data should be const in the first place. Maybe I miss the point here? Looking at flow offload statement for instance, should 'table_name' not be 'char *' instead of using this free_const() to free it? Cheers, Phil
