Thank you for the elaborate reply. To be clear, though: what I am expecting is that the full unsigned 32-bit range be supported, for overall consistency with the built-in bitwise identifiers. That is a much more constrained issue to resolve than restoring any previous general overflow/underflow behavior, which at this point is no longer all that interesting I think (nobody else complained, after all). Given your explanation, I guess that is now more of a feature request than a bug report, but I still think that supporting the full unsigned 32-bit range makes sense. I have changed my script to use $isbit though, so leaving everything as is is also fine with me.
