src/games/grdc/grdc.c, branch main

Final step of eliminating the "games" distribution: Merge src/games

2015-10-02T10:08:11Z

(or what's left of it, at least) into src/usr.bin. This change will not be MFCed. Discussed at: EuroBSDCon 2014 Committed from: EuroBSDCon 2015

Correct grdc(1) 12-hour display between 12:00 and 13:00

2015-06-02T20:53:17Z

PM starts at 12:00, not 13:00. PR: 194291, 200133 Submitted by: Nick Price MFC after: 1 week

Add static keywords to variables and functions where possible in games/.

2011-11-05T07:18:53Z

This allows us to detect unused functions and variables and allows the compiler to do a better job at optimisation.

grdc(6): de-obfuscate the timekeeping of now/delay

2010-08-03T20:56:23Z

- 'now' only contains current time readings - delay is only used as parameter to nanosleep - prev_sec contains the time_t of the previous loop iteration Submitted by: bde MFC after: 2 weeks

grdc(6): Partial backout of r210755

2010-08-03T16:02:57Z

The previous revision was flawed in numerous ways: - the if condition would depend on garbage stack values - grdc(6) would loop n times, not n seconds. This only makes a difference if it takes more than 1 second to recalculate/redraw the display. - style(9) violations The following change adds argument checking and tracks the elapsed time between loops explicitly and will exit after roughly n seconds. While here sort headers and remove bogus #ifndef Submitted by: bde MFC after: 2 weeks

grdc(6): fix timekeeping for user-supplied value n

2010-08-02T12:15:22Z

- Keep timespec 'now' and 'delay' separate to avoid confusion - Increase user-supplied n to run _at least_ n seconds, not max n PR: bin/149130 (based on) Submitted by: Andy Farkas MFC after: 2 weeks

grdc(6) make WARNS=6 clean and bump accordingly

2010-02-15T14:30:37Z

Approved by: ed (Co-mentor)

Improve time precision for grdc(6):

2010-02-10T18:20:20Z

Traditionally, grdc would obtain time through time(3) which in turn gets only the second part of clock (CLOCK_SECOND), and sleep for 1 second after each screen refresh. This approach would have two problems. First, we are not guaranteed to be waken up at the beginning of a whole second, which will typically exhibit as a "lag" on second number. Second, because we sleep for whole second, and the refresh process would take some time, the error would accumulate from time to time, making the lag variable. Make grdc(6) to use time(3) to get time only at the beginning, and sample time in CLOCK_REALTIME_FAST granularity after refreshing, and use the nanosecond part to caculate how much time we want to sleep. PR: bin/120813 MFC after: 1 month

Handle 12-hour clocks properly: when the time is 00:00-00:59, adjust the

2003-06-23T16:01:11Z

hour to 12 so the time reads "12:00-12:59 AM".

Add an option to print the time in 12-hour format.

2003-03-28T16:37:45Z

Submitted by: Samy Al Bahra