On Thu, Nov 7, 2024 at 12:01 PM <michal.lyszc...@bofc.pl> wrote: > On 2024-11-06 10:01:55, Nathan Hartman wrote: > > I am +1 for a Kconfig. > > > > * or just make the default 64-bit on ALL systems, and if you are > > trimming resources, you can make a judgment call whether to reduce it > > to 32-bit > > I would say this. > > I believe defaults should be what works for majority of cases. Things to work > is more important for things to be quick. People of different experience and > knowledge uses this RTOS. A lot of people won't even notice performance hit > from 64bit time, but they will surely notice weird time bugs. > > Having code we know is going to crap out in the near future is kinda strange > design choice. I think you could have ignored it when there was 50 years left, > but this will happen in 14 years which is not that far for embedded systems > that can work for decades.
+1 :-) int64_t time_t as default via kconfig with option to manually switch to int32_t or uint32_t seems most versatile and no surprises :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
