What is namespace pollution?

Question

What does the term \'namespace pollution\' mean and why would making a method static help to prevent it?

This question seems to be similar but relates specifically t

Answer 1

Namespace pollution is a lot like pollution in general. It means that something is misplaced. In programming that means that code that should really live in separate namespaces is added to a common namespace (in some cases the global namespace). This can happen with both static and non static code, so I don't really see a scenario where static helps prevent namespace pollution.

Basically, namespaces' main function is to categorize code, and both static and non static code must be defined in a namespace somewhere.