Separated parts of time and date about ntpclient HOT 3 CLOSED

I just briefly looked at this. While it is nice to have a call for each item I would be concerned about rollover issues. Like the seconds changing from 59 to 0 and then the minute increments. (a bigger concern with higher rollovers) And if the rollover happens between your calls then you end up with the incorrect time. I think it would be better to do one call that populates a structure and then you get to pick out what you need from it. Only one now. Not multiple.

from ntpclient.

Aha, good point. I thought its save all data in variable "moment" filled in one NTP call and then I can pick what I need before next call happen.
I understand now, it is better one call and then parse data from string what I get.

from ntpclient.

I think there is a little misunderstanding of what this library does.

It does not keep or count time, so its intention is not to get time or date from your sketch. That task is performed by Time library by Paul Stroffregen. That's where now() and other functions you need are coded.

NTPClientLib connects a NTP server two times a day, for instance, to keep time in sync. I coded some functions to get string encoded date for my convenience, but it is not library's core.

You don't need to force NTP sync to get time, time keeping and time synchronization are independent tasks done in different libraries.

I'll keep this issue open for the moment if you like to add some comments.

from ntpclient.