Bash Scripting - String Operations
What is wrong with this code snippet?
file="data.txt"
newfile=${file/data/txt}
echo $newfileWhat is wrong with this code snippet?
medium📝 Debug Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Check the replacement syntax
The replacement syntax must be ${var/old/new} with slashes separating parts. Here, ${file/data/txt} is correct syntax.Step 2: Analyze the replacement effect
The code replaces 'data' with 'txt', so 'data.txt' becomes 'txt.txt'. There is no syntax error.Step 3: Identify the logical issue
While the code executes correctly, the replacement of 'data' with 'txt' produces 'txt.txt', which alters the filename in a way that incorrectly impacts the intended file extension handling.Final Answer:
It replaces 'data' with 'txt' but changes the file extension incorrectly. -> Option DQuick Check:
Replacement changes 'data' to 'txt', affecting filename [OK]
Quick Trick: Check slashes and replaced parts carefully for syntax and effect [OK]
Common Mistakes:
MISTAKES- Assuming syntax error when slashes are correct
- Ignoring that replacement changes filename parts
- Confusing replacement with substring extraction
Master "String Operations" in Bash Scripting
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Bash Scripting Quizzes