ShaunR Posted October 26, 2021 Report Share Posted October 26, 2021 12 minutes ago, Rolf Kalbermatter said: size_t is usually according to the platform bitness since it makes little sense to have size parameters that would span more than 4GB on a 32-bit platform. If you need a 64-bit value regardless you need to use the explicit uint64_t. time_t is another type that can be 64-bit even on 32-bit platforms, but it doesn't have to be. It often depends on the platform libraries such as the libc version used or similar things. Yeah. Didn't think I'd get a definitive answer since size_t is only guaranteed to be greater than 15 bits. For MS it is UINT_MAX, which could be anything. The only way to know for certain is to test the compiled environment but even then it depends on things like if functions use 32 modular arithmetic. I don't think it can be resolved conclusively in LabVIEW but the choice is only unsigned pointer sized integer or a conditional case for target bitness. I guess you are alluding to the conditional for "most likely not to fall over in most circumstances" 25 minutes ago, Rolf Kalbermatter said: it makes little sense to have size parameters that would span more than 4GB on a 32-bit platform That's what they said about disk drives and look what happened Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.