GH-125174: Don't use UINT32_MAX in header file

[markshannon]

It breaks a buildbot. Maybe UINT32_MAX isn't defined in their C++ header files.

• Issue: "Immortal" objects aren't immortal and that breaks things. #125174

[markshannon]

!buildbot "AMD64 FreeBSD 3.x"

[bedevere-bot]

The regex '"AMD64 FreeBSD 3.x"' did not match any buildbot builder. Is the requested builder in the list of stable builders?

[markshannon]

!buildbot "AMD64.FreeBSD.3.x"

[bedevere-bot]

The regex '"AMD64.FreeBSD.3.x"' did not match any buildbot builder. Is the requested builder in the list of stable builders?

[markshannon]

!buildbot AMD64.FreeBSD

[bedevere-bot]

🤖 New build scheduled with the buildbot fleet by @markshannon for commit 957cf8a 🤖

The command will test the builders whose names match following regular expression: AMD64.FreeBSD

The builders matched are:

• AMD64 FreeBSD PR
• AMD64 FreeBSD Refleaks PR
• AMD64 FreeBSD14 PR
• AMD64 FreeBSD15 PR

[colesbury]

In case you were wondering why it's missing, like I was:

The C99 standard suggests that C++ implementations should not define the above limit, constant, or format macros unless the macros __STDC_LIMIT_MACROS, __STDC_CONSTANT_MACROS or __STDC_FORMAT_MACROS (respectively) are defined before including the relevant C header (stdint.h or inttypes.h). This recommendation was not adopted by any C++ standard and was removed in C11. However, some implementations (such as glibc 2.17) try to apply this rule, and it may be necessary to define the __STDC macros; C++ compilers may try to work around this by automatically defining them in some circumstances

https://en.cppreference.com/w/cpp/types/integer

[encukou]

Thank you for the fix!