> might be of (some) interest for AVRs would be time_t (which is a
> signed 32-bit integer, mostly for historical reasons).
Do we care about "the Year 2038 problem (Y2K38)" when it becomes negative?
There are a couple of more obscure date roll over issues that happen before
those, but they don't show up in embedded code.
--
http://www.wearablesmartsensors.com/
http://www.softwaresafety.net/ http://www.designer-iii.com/
http://www.unusualresearch.com/
_______________________________________________
AVR-libc-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
