Enclose code in a namespace to avoid polluting the global namespace

[GiovanniDicanio]

It seems to me that several class templates and enums from the SafeInt.hpp header pollute the global namespace. There should be a safeint namespace enclosing those, including the SafeInt class template.

[GiovanniDicanio]

This code should fix the above issue (please note that the code requires more testing).
SafeInt_GiovanniDicanio_2023_10_26.zip

[GiovanniDicanio]

Attached code with parenthesized (std::numeric_limits<T>::max)() and (std::numeric_limits<T>::min)() to fix #58 #51 .
(Please note that the code requires more testing).
SafeInt_GiovanniDicanio_2023_10_30.zip

[dcleblanc]

Please send code as a pull request. There's not a lot that isn't either named with some variant of safeint, or is otherwise unlikely to collide. The code has been out for 20 years, and excepting a conflict between a very non-standard Windows macro and the STL, there hasn't been an issue yet.

I'll look into doing this later, but this falls into the tidiness category.

[GiovanniDicanio]

Thanks for your attention! I think names like IntRegion or ComparisonMethod, and several others, should be better nicely enclosed in a safeint ad hoc namespace. Similar for adding some proper prefix (like SAFEINT_) to the unprefixed preprocessor macros (like CLANG_COMPILER, UNKNOWN_COMPILER, etc.) defined in SafeInt.hpp header. I did note that there are also preprocessor macros properly prefixed, like SAFEINT_CONSTEXPR14. Thank you!