Cristian Maglie

> Perhaps the (implicit) truncated could be improved to do proper rounding, which would round 0.5 to 1 instead of 0, which is probably the proper solution for this problem?...

No it can't be closed, there isn't still a good solution to this problem. Just to make it more clear, you can try the following test on your PC: ```...

Can someone post the function for AVR? Does anyone has the equivalent for the other architectures?

> The RealtimeClock class is actually managing time so it should be called ArduinoTime this brings a more wider question: are we going to provide the time API (and also...

> Whew, long message. Hopefully some of this helps? In a week or so, I can actually work with the code... Paul, thanks for taking the time to write this...

> Atomic access is a real issue with the current Time library. The simple functions year(), month(), day(), hour(), minute(), second() are convenient, but when called in sequence, especially when...

Ok I've had some time to tinker on this one, hope that the latest changes reflect better how I would like to see this API evolve and that those changes...

The reference page https://www.arduino.cc/reference/en/language/functions/advanced-io/shiftout/ proposes: ```if you’re interfacing with a device that’s clocked by rising edges, you’ll need to make sure that the clock pin is low before the call...

The readme **suggests** to symlink, but everyone can use any other solution they like, including submodules. About our repos, I personally don't like submodules, but if it's only me then...

Related issues: https://github.com/arduino/Arduino/issues/3614 https://github.com/arduino/Arduino/pull/3651 /cc @facchinm @matthijskooijman @stickbreaker