Long option parsing in Bash Scripting - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of a script parsing long options with getopts

What is the output of this Bash script when run with arguments --name=John --age=30?

Bash Scripting

#!/bin/bash
while getopts ":-:" opt; do
  case $opt in
    -)
      case $OPTARG in
        name=*)
          name=${OPTARG#*=}
          echo "Name: $name"
          ;;
        age=*)
          age=${OPTARG#*=}
          echo "Age: $age"
          ;;
        *)
          echo "Unknown option: --$OPTARG"
          ;;
      esac
      ;;
    *)
      echo "Invalid option: -$OPTARG"
      ;;
  esac
done

A

Name: John
Age: 30

B

Unknown option: --name=John
Unknown option: --age=30

C

Name: --name=John
Age: --age=30

D

Invalid option: -n
Invalid option: -a

💡 Hint

Look at how the script extracts values after the '=' sign in long options.

The script uses getopts with a special case for '-' to parse long options. It extracts the value after '=' and prints it. So, it correctly prints 'Name: John' and 'Age: 30'.

📝 Syntax

intermediate

Identify the syntax error in long option parsing

Which option contains a syntax error that prevents parsing long options correctly?

Bash Scripting

while getopts ":-" opt; do
  case $opt in
    -)
      case $OPTARG in
        name=*)
          name=${OPTARG#*=}
          echo "Name: $name"
          ;;
        age=*)
          age=${OPTARG#*=}
          echo "Age: $age"
          ;;
        *)
          echo "Unknown option: --$OPTARG"
          ;;
      esac
      ;;
    *)
      echo "Invalid option: -$OPTARG"
      ;;
  esac
done

A Missing quotes around variable expansions in echo statements

B Using $OPTARG instead of $OPTIND inside the case statement

C Incorrect variable expansion syntax: ${OPTARG#*=} should be ${OPTARG:=*}

D Missing colon after '-' in getopts string: ":-" should be ":-:"

💡 Hint

Check the getopts option string carefully.

The getopts string must include a colon after '-' to enable long option parsing. Without it, getopts won't recognize long options properly.

🔧 Debug

advanced

Why does this long option parsing script fail to capture option values?

Given this script snippet, why does it fail to print the expected values when run with --file=example.txt?

while getopts ":-:" opt; do
  case $opt in
    -)
      case $OPTARG in
        file)
          file=$2
          echo "File: $file"
          shift 2
          ;;
        *)
          echo "Unknown option: --$OPTARG"
          ;;
      esac
      ;;
  esac
done

A Missing colon after 'file' in getopts string to accept an argument

B Using $2 inside getopts loop is invalid; should use $OPTARG instead

C The script expects the value as a separate argument, but the option is passed as --file=example.txt

D The shift command inside the case breaks the getopts loop prematurely

💡 Hint

Think about how getopts treats options with '=' signs.

When using long options with '=' (like --file=example.txt), getopts treats the entire string as one argument. The script incorrectly expects the value in $2, but it is part of $OPTARG.

🚀 Application

advanced

Write a snippet to parse --mode= and --verbose long options

Which code snippet correctly parses --mode=fast and --verbose options using getopts in Bash?

A

while getopts ":-:" opt; do
  case $opt in
    -)
      case $OPTARG in
        mode=*)
          mode=${OPTARG#*=}
          ;;
        verbose)
          verbose=1
          ;;
      esac
      ;;
  esac
done

B

while getopts ":m:v" opt; do
  case $opt in
    m)
      mode=$OPTARG
      ;;
    v)
      verbose=1
      ;;
  esac
done

C

while getopts ":-:" opt; do
  case $opt in
    -)
      case $OPTARG in
        mode)
          mode=$2
          shift 2
          ;;
        verbose)
          verbose=1
          ;;
      esac
      ;;
  esac
done

D

while getopts ":-:" opt; do
  case $opt in
    -)
      case $OPTARG in
        mode=*)
          mode=$OPTARG
          ;;
        verbose=*)
          verbose=$OPTARG
          ;;
      esac
      ;;
  esac
done

💡 Hint

Remember that options with '=' need to be parsed from $OPTARG.

Option A correctly parses --mode=fast by extracting the value after '=' and sets verbose flag when --verbose is passed without value.

🧠 Conceptual

expert

Why is getopts limited for complex long option parsing?

Which statement best explains why getopts is not ideal for parsing complex long options in Bash scripts?

A getopts automatically converts all long options to short options internally, causing conflicts

B getopts does not natively support long options with optional or multiple arguments and requires complex workarounds

C getopts requires external libraries to parse any options longer than one character

D getopts cannot parse any options starting with a dash (-) and only works with positional arguments

💡 Hint

Think about the design and limitations of getopts.

getopts was designed for short options and does not handle long options with optional or multiple arguments well, so scripts must use complex parsing logic or other tools.