{"id":3411,"date":"2018-12-22T00:01:08","date_gmt":"2018-12-22T08:01:08","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=3411"},"modified":"2019-11-23T21:57:08","modified_gmt":"2019-11-24T05:57:08","slug":"tick-tock-goes-the-clock-part-ii","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=3411","title":{"rendered":"Tick-Tock Goes the Clock, Part II"},"content":{"rendered":"

From last week’s Lesson<\/a>, the code I wrote for my clock program outputs the current hour and minute. I also want it to update, to keep running and output the next minute and so on. To me, that’s the difference between a clock program and code that just outputs the current time.
\n
\nAn updating clock program requires some sort of loop. In the following code, I add a loop to the program:<\/p>\n

#include <stdio.h>\r\n#include <time.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    }\r\n\r\n    return(0);\r\n}<\/pre>\n
The code is identical, save for the addition of the endless while<\/em> loop. Rather than display the time in discrete minute values, the output is a continuous stream of text:<\/p>\n
It is now 12:25
\nIt is now 12:25
\nIt is now 12:25
\nIt is now 12:25
\nIt is now 12:25
\n...<\/code><\/p>\n
Eventually, the time changes. This program qualifies as a clock, but it’s not what I had in mind. Instead, I want to see output like this:<\/p>\n
It is now 12:25
\nIt is now 12:26
\nIt is now 12:27
\n...<\/code><\/p>\n
The output above ticks every minute, updating the clock program’s output with the system time. To make this possible, a second loop is required. I would encourage you to try to concoct the second loop on your own. That’s because it’s not the easiest thing to do, though once you see the answer it makes sense.<\/p>\n
Yes<\/em>! Go off and figure out the second loop, the one that delays output for a minute. Do it on your own!<\/p>\n
I’ll wait.<\/p>\n
[ ♪ musical interlude<\/em> ♫ ]<\/p>\n
Did you do it? Probably not. Anyway.<\/p>\n
Consider that the time_t<\/em> value represents seconds ticked. So to make output pause for one minute, I add 60 to the time_t<\/em> value stored in the now<\/code> variable and then wait for the output of the time()<\/em> function to be greater than or equal to that value. Here is the test:<\/p>\n
while( now+60 > time(NULL) )
\n    ;<\/code><\/p>\n
In the while<\/em> loop’s test, 60 seconds are added to the value of now<\/code>. The time(NULL)<\/code> expression returns the current clock tick value. So the loop waits 60 seconds; when time(NULL)<\/code> returns a value 60 seconds in the future, the loop stops. At that point, the next clock value is output:<\/p>\n
It is now 12:32
\nIt is now 12:33
\nIt is now 12:34
\nIt is now 12:35
\nIt is now 12:36
\n^C<\/code><\/p>\n
Click here<\/a> to view the complete code.<\/p>\n
With a little output modification, I have my clock program. I just noticed one problem: The clock’s time wasn’t in sync with the system time. I checked the seconds elapsed, and discovered that the code counts the next minute based on when the program starts, not when the system clock hits :00 seconds. The surprising thing is that only one change is required to fix this problem \u2014 and it might even be something you came up with, if you worked on your own solution to determining how to implement the second loop.<\/p>\n
See next week’s Lesson<\/a> for the solution.<\/p>\n","protected":false},"excerpt":{"rendered":"
Outputting and updating the current 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-3411","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\/3411","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=3411"}],"version-history":[{"count":8,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3411\/revisions"}],"predecessor-version":[{"id":3881,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3411\/revisions\/3881"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3411"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3411"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3411"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}