Parsing numeric arguments - Step-by-Step Execution

Concept Flow - Parsing numeric arguments

Start: Receive argument as string

↓

Check if string is numeric

↓

Convert string

↓

Store numeric value

↓

Use numeric value in program

↓

End

The program receives a string argument, checks if it is numeric, converts it to a number if valid, and then uses it.

Execution Sample

C

#include <stdio.h>
#include <stdlib.h>

int main(int argc, char *argv[]) {
    if (argc < 2) {
        printf("Error: No argument provided.\n");
        return 1;
    }
    int num = atoi(argv[1]);
    printf("Number: %d\n", num);
    return 0;
}

This code takes the first command line argument, converts it to an integer, and prints it.

Execution Table

Step	Action	Input	Result	Notes
1	Program starts	argc=2, argv[1]="42"	Ready to parse	Program receives argument as string
2	Call atoi(argv[1])	"42"	42	String converted to integer 42
3	Store result in num	42	num=42	Integer stored in variable
4	Print num	num=42	Output: Number: 42	Number printed to console
5	Program ends	-	-	Normal termination

💡 Program ends after printing the converted number

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
argc	2	2	2	2
argv[1]	"42"	"42"	"42"	"42"
num	undefined	undefined	42	42

Key Moments - 2 Insights

Why does atoi return 0 if the argument is not a number?

atoi returns 0 when the string does not start with a valid number, as shown in step 2 where conversion fails silently.

What happens if no argument is given?

If argc < 2, argv[1] does not exist, so accessing it causes undefined behavior; the program should check argc first.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of num after step 3?

A 0

B 42

C undefined

D "42"

💡 Hint

Check the 'Result' column in row for step 3 in execution_table

At which step does the program print the output?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look for the row with 'Print num' action in execution_table

If argv[1] was "abc", what would atoi(argv[1]) return?

A 42

B -1

C 0

D Error

💡 Hint

Recall atoi returns 0 when string is not numeric, as explained in key_moments

Concept Snapshot

Parsing numeric arguments in C:
- Arguments come as strings (argv[])
- Use atoi() to convert string to int
- atoi returns 0 if string is not numeric
- Always check argc before accessing argv
- Use the int value in your program after conversion

Full Transcript

This example shows how a C program parses a numeric argument from the command line. The program receives arguments as strings in argv. It uses the function atoi to convert the first argument string to an integer. The execution flow starts by receiving the argument, then checking and converting it with atoi. The converted integer is stored in a variable and printed. If the argument is not numeric, atoi returns 0 silently. The program ends after printing the number. Beginners should remember to check the number of arguments before accessing argv to avoid errors. This trace helps visualize each step and variable change during parsing.

Practice

1. What does the atoi function do in C when parsing numeric arguments?

easy

A. Converts a string to an integer without error checking

B. Converts a string to a floating-point number

C. Checks if a string contains only digits

D. Parses a string and returns a pointer to the next character

Solution

1. Step 1: Understand atoi function purpose

   atoi converts a string to an integer but does not check for errors or invalid input.

2. Step 2: Compare with other parsing functions

   Unlike strtol, atoi does not provide error detection or pointer to next character.

3. Final Answer:

   Converts a string to an integer without error checking -> Option A

4. Quick Check:

   atoi = simple integer conversion [OK]

Hint: Remember: atoi converts but doesn't check errors [OK]

Common Mistakes:

• Thinking atoi checks for invalid input
• Confusing atoi with strtol
• Assuming atoi returns pointer to next char

2. Which of the following is the correct syntax to parse a string "1234" to an integer using strtol in C?

easy

A. int num = strtol("1234", NULL, 10);

B. long num = strtol("1234", NULL, 10);

C. long num = atoi("1234", NULL, 10);

D. int num = strtol("1234", 10, NULL);

Solution

1. Step 1: Check strtol return type

   strtol returns a long, so the variable must be long.

2. Step 2: Verify argument order

   Arguments are: string, pointer to char* for end, and base (10 for decimal). So strtol("1234", NULL, 10) is correct.

3. Final Answer:

   long num = strtol("1234", NULL, 10); -> Option B

4. Quick Check:

   strtol returns long, args: string, endptr, base [OK]

Hint: Remember strtol returns long, not int [OK]

Common Mistakes:

• Using int instead of long for strtol result
• Mixing argument order in strtol
• Using atoi syntax with strtol

3. What will be the output of this C code snippet?

#include 
#include 

int main() {
    char *str = "42abc";
    char *endptr;
    long val = strtol(str, &endptr, 10);
    printf("%ld %s\n", val, endptr);
    return 0;
}

medium

A. Error

B. 0 42abc

C. 42abc (null)

D. 42 abc

Solution

1. Step 1: Understand strtol parsing behavior

   strtol converts initial numeric part "42" to long and sets endptr to point after parsed number, which is "abc".

2. Step 2: Analyze printf output

   It prints the number 42 and then the string starting at endptr, which is "abc".

3. Final Answer:

   42 abc -> Option D

4. Quick Check:

   Parsed number + leftover string = 42 abc [OK]

Hint: Check where endptr points after strtol [OK]

Common Mistakes:

• Assuming strtol parses entire string
• Ignoring endptr usage
• Expecting error on non-digit suffix

4. Identify the error in this code snippet that parses a numeric argument:

#include 

int main(int argc, char *argv[]) {
    int num = atoi(argv[1]);
    if (num == 0) {
        printf("Invalid number\n");
    }
    return 0;
}

medium

A. Missing check if argc > 1 before accessing argv[1]

B. Using int instead of long for atoi result

C. atoi returns 0 for invalid input and valid zero, causing confusion

D. No error, code is correct

Solution

1. Step 1: Check argument count before access

   The code uses argv[1] without verifying argc > 1, risking out-of-bounds access.

2. Step 2: Understand atoi zero ambiguity

   While atoi returns 0 for invalid input and valid zero, the bigger issue is missing argument check causing runtime error.

3. Final Answer:

   Missing check if argc > 1 before accessing argv[1] -> Option A

4. Quick Check:

   Always check argc before argv access [OK]

Hint: Always check argc before argv usage [OK]

Common Mistakes:

• Ignoring argc check leads to crashes
• Confusing atoi zero return meaning
• Assuming atoi handles errors

5. You want to safely parse a command-line argument as a positive integer in C. Which approach correctly handles invalid input and zero?

#include <stdio.h>
#include <stdlib.h>

int main(int argc, char *argv[]) {
    if (argc <= 1) {
        printf("No input provided\n");
        return 1;
    }
    char *endptr;
    long val = strtol(argv[1], &endptr, 10);
    if (*endptr != '\0' || val <= 0) {
        printf("Invalid positive integer\n");
        return 1;
    }
    printf("Parsed value: %ld\n", val);
    return 0;
}

hard

A. Fails to check if argv[1] is NULL before parsing

B. Does not handle negative numbers correctly

C. Correctly parses positive integers and rejects invalid or zero input

D. Should use atoi instead of strtol for safety

Solution

1. Step 1: Check argument count

   The code checks if argc <= 1 to ensure input is provided.

2. Step 2: Use strtol with endptr to detect invalid characters and check if value is positive

   It verifies *endptr == '\0' to confirm full string parsed and val > 0 to ensure positive integer.

3. Final Answer:

   Correctly parses positive integers and rejects invalid or zero input -> Option C

4. Quick Check:

   strtol + endptr + value check = safe parsing [OK]

Hint: Use strtol with endptr and check value > 0 [OK]

Common Mistakes:

• Using atoi which can't detect invalid input
• Not checking endptr for leftover chars
• Ignoring zero or negative values