YOUR C LEARNING COMPANION

Kahan se padhein?

Learning path
Input ke saath kaamChapter 57 of 73

Dates, clocks aur time measurement

Calendar time, local display, processor time, elapsed duration, resolution aur C23 clock support alag karein.

5 min readDevelopingC17 baseline
Offline reading
Is chapter mein8 sections

“Aaj date kya hai?” aur “Is work mein kitna time laga?” alag questions hain. Ek ke liye suitable clock doosre ke liye unsuitable ho sakti hai. C calendar aur processor-time facilities deta hai; result interpret karne se pehle availability aur behavior check karein.

1. Needed time ka type batayein

Calendar time instant ko calendar-related scale par locate karta hai. Elapsed time events ke beech duration hai. Processor time used execution resources measure karta hai; waiting se elapsed time badh sakta hai bina same processor time use kiye. Time zone calendar display badalta hai; elapsed duration ki nayi unit nahi.

Monotonic clock apne stated contract ke under backward nahi chalti. Calendar clocks adjust ho sakti hain. Resolution reported readings ki granularity hai; yeh accuracy, monotonicity ya small operation ka nonzero measured duration prove nahi karti.

2. Calendar fields ke conventions hain

struct tm broken-down calendar representation hai. tm_year 1900 se years count karta hai aur tm_mon months zero se count karta hai. Human notation se in conventions ko mix karne par off-by-one aur year-related mistakes hoti hain. Fixed-date example formatting par focus karta hai; current date nahi poochhta.

Complete C17 program
#include <assert.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <time.h>

int main(void)
{
    struct tm date = {
        .tm_year = 2024 - 1900, .tm_mon = 0, .tm_mday = 2,
        .tm_hour = 0, .tm_min = 0, .tm_sec = 0,
        .tm_wday = 2, .tm_yday = 1, .tm_isdst = 0
    };
    char text[32];
    size_t length = strftime(text, sizeof text, "%Y-%m-%d", &date);
    if (length == 0) return EXIT_FAILURE;
    assert(strcmp(text, "2024-01-02") == 0);
    if (puts(text) == EOF) return EXIT_FAILURE;
    return EXIT_SUCCESS;
}

strftime success par terminating null ke bina stored characters ki count return karta hai. Is nonempty date format mein zero ko failure maankar buffer print na karein. General case mein legitimately empty expansion bhi zero return kar sakti hai. Textual names LC_TIME par depend kar sakte hain. Example unchanged startup C locale aur numeric date fields use karta hai.

3. Calendar acquisition aur conversion check karein

time time_t calendar value deta hai aur unavailability par (time_t)-1. time_t ko hamesha Unix seconds ya fixed-width value na samjhein. difftime valid calendar values ka difference seconds mein deta hai; unknown representation par direct subtraction portable substitute nahi hai.

gmtime aur localtime calendar values convert karte hain aur fail ho sakte hain. Returned storage later related calls reuse kar sakti hain; needed result ko next conversion se pehle copy karein. mktime broken-down value ko local time maanta aur fields normalise kar sakta hai. Daylight-saving transitions mein local times ambiguous ya missing ho sakte hain. Sirf date string ek unique instant identify na kar paaye, aisa ho sakta hai.

4. Processor time waiting ka stopwatch nahi hai

clock program ka approximate used processor time deta hai, ya unavailable ho toh (clock_t)-1. Valid clock-tick difference ko seconds mein express karne ke liye suitable arithmetic se CLOCKS_PER_SEC se divide karte hain. Readings ki range aur wrap limits hain; short interval zero dikh sakta hai. Subtraction se pehle type ki usable range aur platform clock contract establish karein.

C17 timespec_get ke liye TIME_UTC base require karta hai. Successful call calendar seconds aur nanoseconds fill karti hai. Monotonic elapsed-time measurement promise nahi hoti. Neeche probe current reading predict kiye bina success aur specified nanosecond range check karta hai.

Complete C17 program
#include <assert.h>
#include <stdlib.h>
#include <time.h>

int main(void)
{
    struct timespec now;
    if (timespec_get(&now, TIME_UTC) != TIME_UTC) return EXIT_FAILURE;
    assert(now.tv_nsec >= 0 && now.tv_nsec <= 999999999L);
    return EXIT_SUCCESS;
}

5. Measurement ke saath meaning rakhein

Logs ke liye time scale, zone aur format decide karein. Performance ke liye intended resource wali clock, resolution se zyada work aur measurement overhead consider karein. Deadlines ke liye relevant API ka clock aur wait contract use karein. Sirf “time” label saari choices nahi batata.

Sochkar dekhein

Operation file ke liye two seconds wait kare toh kya clock two seconds processor time report karega?

Explanation padhein

Nahi. Waiting duration aur processor time alag quantities hain. Waiting question ke liye suitable elapsed-time clock choose karein.

Primary references aur aage padhne ke links

Aage badhne se pehle

  • Calendar time, elapsed duration aur processor time alag questions ke answers hain.
  • Calendar fields, conversions aur formatting ke conventions aur failure cases hain.
  • Clock availability, resolution, range aur monotonicity separately check karein.
In ideas ko alag rakhein
Clock resolution / Clock accuracy
Fine reported units intended quantity ki accurate ya monotonic measurement establish nahi karte.
Apne words mein samjhaayein

Two seconds wait karne wala program bahut kam processor time kyun use kar sakta hai?

Optional: bolkar samjhein ya note rakhein. Tayyar hon toh aage badh sakte hain.

Apni understanding check karein

Optional hai. Answers save ya send nahi hote; chapter kabhi lock nahi hota.

clock() kya measure karne ka attempt karta hai?
Har choice ki explanation padhein
  1. Hamesha calendar date, Unix seconds mein.

    Calendar time aur time_t representation, clock ke interface se alag hain.

  2. Program ka used processor time, general wall-clock stopwatch nahi.

    ✓ Sahi reasoning. Interface ki limits ke saath availability check karein aur CLOCKS_PER_SEC se conversion karein.

  3. Executed source lines ki count.

    Yeh clock interface source-line count report nahi karta.

C17

Agla idea padhne ke liye tayyar?

Mark this chapter as read whenever you feel ready.

CHAPTER 57 / 73

Is chapter mein

Dates, clocks aur time measurement

Search all 73 chapters in both languages.EN + HG

Try “pointer”, “why int”, or “undefined behavior”.

Concepts connect. Follow your curiosity.↑ ↓ to explore · Enter to open
MAKE YOURSELF COMFORTABLE

Your reading space

Appearance

A clear canvas with balanced contrast.

Text size

100%
AA

Reading tools

Your data stays in this browser

Export a backup before changing browsers or replacing an older version of the reader.

YOUR PERSONAL MARGINS

My notebook

Saved on this device
A LITTLE CLARITY

The glossary

A starting meaning, then a chapter to go deeper.

A QUICK DEFINITION

A little clarity

Read the full explanation →

A thought worth keeping