4 ms·
Macros are often a bad idea for defining types. If you do #define INT_PTR int* INT_PTR p, q; the code is actively misleading. Is there a better way to
by ramshorns 10y ago
Macros are often a bad idea for defining types. If you do
#define INT_PTR int*
INT_PTR p, q;
the code is actively misleading. Is there a better way to do it for function pointers?
- flukus 10y agoThere are a few other problems with multiple declarations aren't there? I though they were discouraged in c.