Here, max is not local to function foo. It's effectively global. You can't declare a macro as a member of a C++ class or namespace. In a sense, macro names are more pervasive (read “worse”) than ...

Does it ever make sense to declare a variable in C or C++ as both volatile (in other words, “ever-changing”) and const (“read-only”)? If so, why? And how should you combine volatile and const properly ...