Arguments, conversion aur environment
argc/argv bounds check, strtol se numeric text validate aur environment strings ko borrowed external input treat karein.
Is chapter mein7 sections
Program start hote waqt input maangne se pehle bhi information le sakta hai. Command-line arguments strings hote hain, isliye number jaisa argument bhi parse aur validate karna padta hai. Environment ki information ke alag rules hain.
1. Hosted main interface samjhein
Portable hosted forms mein int main(void) aur int main(int argc, char *argv[]), ya equivalent forms hain. Parameter declaration mein char *argv[], char **argv mein adjust hota hai. Other implementation-defined startup forms exist kar sakti hain; third environment parameter universally portable standard form nahi. Freestanding startup ke rules different hain.
| Expression | Guarantee ya condition |
|---|---|
argc | Nonnegative; zero allowed hai. |
argv[argc] | Null pointer sentinel, empty string nahi. |
argv[0] | Sirf argc > 0 par: program-name string, name unavailable ho toh empty ho sakti hai. |
argv[1] | argc > 1 check ke baad hi usable argument string. |
Valid i ka argv[i] | Null-terminated argument string ko point karta hai; null pointer sentinel ki string contents nahi. |
2. Argument use se pehle count check karein
#include <stdio.h>
int main(int argc, char *argv[])
{
if (argc > 1) {
printf("first=%s\n", argv[1]);
} else {
puts("no input argument");
}
return 0;
}
Format string fixed hai aur argument %s ko pass hota hai; argument text ko printf format nahi banaya gaya. Input argument absent ho toh argv[1] read kiye bina alternative path chalta hai. Real command-line interface ko extra arguments allowed hain ya nahi bhi specify karna chahiye. Next example exactly one require karta hai.
Hosted rules mein argument strings modifiable hain aur program termination tak last-stored values retain karti hain. Yeh getenv ki borrowed, nonmodifiable storage se different hain. Shell, launcher ya operating system typed text ko argument strings mein convert karta hai. Quotes, wildcards aur escape characters C ke main interface se parse nahi hote. Many shells mein quoted phrase ek space wali string bhejta hai; quotation marks usually shell remove karta hai. Details launcher ke rules hain, portable C ke nahi.
3. Numeric text ko conversion aur validation chahiye
"12" containing argv[1] already integer twelve nahi. atoi convenient hai par conversion errors reliably report nahi kar sakta; result represent na ho toh undefined behavior hai. strtol conversion kahan stop hui expose karta hai aur errno se range failure report karta hai. Example decimal one se hundred accept karta hai, optional leading whitespace/sign ke saath, aur trailing characters allow nahi karta.
#include <errno.h>
#include <stdbool.h>
#include <stdio.h>
#include <stdlib.h>
static bool parse_count(const char *text, long *result)
{
if (text == NULL || result == NULL) return false;
char *end = NULL;
errno = 0;
long value = strtol(text, &end, 10);
if (end == text || *end != '\0' || errno == ERANGE) return false;
if (value < 1 || value > 100) return false;
*result = value;
return true;
}
int main(int argc, char *argv[])
{
long count = 0;
if (argc != 2 || !parse_count(argv[1], &count)) {
fputs("Provide one count from 1 through 100.\n", stderr);
return EXIT_FAILURE;
}
printf("count=%ld\n", count);
return EXIT_SUCCESS;
}
Short-circuit ||, argc == 2 hone par hi argv[1] evaluate hone deta hai. Helper mein end == text no conversion hai; *end != '\0' leftover text reject karta hai; ERANGE long ki range ke bahar result reject karta hai. Final range check application ka smaller domain enforce karta hai. Saare checks ke baad hi helper result write karta hai.
Empty string, 12tail, trailing space, huge number, zero aur 101 reject hote hain. Leading whitespace aur +12 stated contract ke according accepted hain; digits-only format chahiye toh explicit lexical check add karein, strtol se silently assume na karein. EXIT_SUCCESS aur EXIT_FAILURE host ko completion status dete hain; exact external representation implementation-defined hai.
4. Environment strings borrowed configuration hain
const char *setting = getenv("CODEDILE_THEME");
const char *theme = setting == NULL ? "default" : setting;
getenv aur NULL ke liye <stdlib.h> include karein. Lookup string pointer return karta hai, variable absent ho toh null pointer; existing empty value aur absence different hain. Returned string modify ya free na karein. Later getenv call pointed-to string overwrite kar sakti hai. Independent lifetime chahiye toh needed contents program-owned storage mein copy karein aur appropriate size/allocation failure check karein.
Arguments aur environment values automatically trustworthy nahi. Explicit accepted values ke saath external input treat karein. Standard C lookup ke liye getenv deta hai, lekin universal setenv function ya variables create karne ki universal shell syntax nahi. Platform extensions ke apne portability aur concurrency rules chahiye.
Primary references aur aage ki reading
- WG14 N1570 — public C11 committee draft: 5.1.2.2.1, 5.1.2.2.3, 6.7.6.3p7, 7.22.1, 7.22.1.4, 7.22.4, 7.22.4.6. C17 baseline ke stable core rules ke liye; final ISO publication nahi.
Aage badhne se pehle
- Command-line arguments hosted startup interface se aayi strings hain.
- Number parse karna aur application value accept karna alag checks hain.
- Borrowed environment strings ke availability aur invalidation rules hain.
In ideas ko alag rakhein
- Numeric-looking text / Valid number
- Partial conversion, overflow, unwanted sign ya out-of-domain value numeric-looking input ko unacceptable bana sakti hai.
Ek command-line argument ko zero se 100 level accept karne se pehle kya check karenge?
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.
Har choice ki explanation padhein
- Haan, argv numeric-looking text automatically convert karta hai.
argv strings deta hai; numeric validation nahi karta.
- Nahi. Parse karke accepted syntax aur range check karein.
✓ Sahi reasoning. Presence, conversion success aur acceptable value range alag checks hain.
- Haan, argc har argument ki numeric value record karta hai.
argc arguments count karta hai; unka numeric content nahi batata.
C17
Earlier edition ka quick reference
Existing section links aur saved passages ke liye retained. Expanded explanation upar hai; documented corrections source review mein recorded hain.
Hosted program mein argc nonnegative hai; zero allowed hai. argv[argc] null pointer hai. Sirf argc > 0 par argv[0] program-name string ko point karta hai; naam unavailable ho toh string empty ho sakti hai. argv[1] read karne se pehle argc > 1 check karein. <stdlib.h> ka getenv("VAR_NAME") environment string ka pointer deta hai, ya absent hone par NULL. Returned string modify/free na karein; independent storage chahiye toh copy karein.
Agla idea padhne ke liye tayyar?
Mark this chapter as read whenever you feel ready.