On 11/7/2024 12:57 AM, Takashi Yamamoto wrote:
That is a good decision too. Remember that with using uint32_t as NuttX always has, there is no year 2038 issue. That issue would only occur if we go to int32_t which has one bit less of range.my suggestion is to keep our time_t unsigned for now and revisit when/if we solve the issues of targets w/o 64-bit integers. (either by improving the toolchains, or stop supporting those targets, or inventing a way to workaround the year 2038 issue.)
