{"id":3421,"date":"2018-12-29T00:01:14","date_gmt":"2018-12-29T08:01:14","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=3421"},"modified":"2018-12-22T12:00:01","modified_gmt":"2018-12-22T20:00:01","slug":"tick-tock-goes-the-clock-part-iii","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=3421","title":{"rendered":"Tick-Tock Goes the Clock, Part III"},"content":{"rendered":"

My clock program is almost complete! It generates the current time as output and it updates the current time every minute. The only step remaining is to synchronize the program’s output with the system time. I want to ensure that when the system reads :00 seconds that the program ticks over to the next minute.
\n
\nThe modification to the code from last week’s Lesson<\/a> is cinchy. It’s a change to Line 20 in the code, the second while<\/em> loop that pauses until the next minute occurs:<\/p>\n

while(time(NULL)%60)
\n    ;<\/code><\/p>\n

The time(NULL)<\/code> expression returns the current clock tick value, the number of seconds elapsed since midnight January 1, 1970. The value ends in a multiple of 60 as one minute clicks to the next. So if you use the expression %60<\/code> (mod sixty), the while<\/em> statement returns true only when the clock ticks to the next minute. This is exactly the condition I need to keep my clock program’s output in sync with the system clock.<\/p>\n

Click here<\/a> to view the entire code.<\/p>\n

The program’s output, however, is less than desirable. The initial line is output fine, but once the top of the minute hits, the output streams for a second and makes me unhappy. That’s because the code runs so fast that the next minute holds while the clock tick value is still true for time(NULL)%60<\/code>.<\/p>\n

To remove the streaming output for that one second, a delay must be added to the code. After the :00 minute occurs, the code must pause for over one second. To add the pause, I used the sleep()<\/em> function, which is prototyped in the unistd.h<\/code> header file. I inserted the following line before the inner while<\/em> loop:<\/p>\n

sleep(2);<\/code><\/p>\n

Here’s the full code:<\/p>\n

\r\n#include <stdio.h>\r\n#include <time.h>\r\n#include <unistd.h>\r\n\r\nint main()\r\n{\r\n    time_t now;\r\n    struct tm *clock;\r\n\r\n    while(1)\r\n    {\r\n        \/* fetch the current time *\/<\/span>\r\n        time(&now);\r\n        \/* fill the time structure *\/<\/span>\r\n        clock = localtime(&now);\r\n        \/* display the clock *\/<\/span>\r\n        printf(\"It is now %2d:%02d\\n\",\r\n                clock->tm_hour,\r\n                clock->tm_min\r\n              );\r\n        \/* delay *\/<\/span>\r\n        sleep(2);\r\n        \/* wait until the next minute *\/<\/span>\r\n        while(time(NULL)%60)\r\n            ;\r\n    }\r\n\r\n    return(0);\r\n}<\/pre>\n
The problem with this solution is that not every compiler implements the sleep()<\/em> function. If not, you can add a delay such as:<\/p>\n
while( now+2 > time(NULL) )
\n    ;<\/code><\/p>\n
The above loop easily replaces the sleep(2)<\/code> statement, adding a 2-second pause to the program and preventing the top-of-the-minute streaming ugliness.<\/p>\n
With this final change, my clock program is complete: It displays the current time, updating at the top of the minute in coordination with the system clock.<\/p>\n","protected":false},"excerpt":{"rendered":"
Keep the clock’s time in sync with the system time. Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-3421","post","type-post","status-publish","format-standard","hentry","category-main"],"_links":{"self":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3421","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3421"}],"version-history":[{"count":3,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3421\/revisions"}],"predecessor-version":[{"id":3438,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3421\/revisions\/3438"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3421"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3421"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3421"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}