Backticks vs braces in Bash

by

The `` is called Command Substitution and is equivalent to $() (parenthesis), while you are using ${} (curly braces).

So all of these expressions are equal and mean “interpret the command placed inside”:

joulesFinal=`echo $joules2 \* $cpu | bc`
joulesFinal=$(echo $joules2 \* $cpu | bc)
#            v                          v
#      ( instead of {                   v
#                                 ) instead of }

While ${} expressions are used for variable substitution.

Note, though, that backticks are deprecated, while $() is POSIX compatible, so you should prefer the latter.

From man bash:

Command substitution allows the output of a command to replace the
command name. There are two forms:

          $(command)
   or
          `command`

Also, `` are more difficult to handle, you cannot nest them for example. See comments below and also Why is $(…) preferred over ... (backticks)?.

More Related Contents:

  1. How to avoid bash command substitution to remove the newline character?
  2. How to address error “bash: !d’: event not found” in Bash command substitution [duplicate]
  3. When does command substitution spawn more subshells than the same commands in isolation?
  4. How can I check if a directory exists in a Bash shell script?
  5. How do I parse command line arguments in Bash?
  6. How do I set a variable to the output of a command in Bash?
  7. Read a file line by line assigning the value to a variable [duplicate]
  8. What is indirect expansion? What does ${!var*} mean?
  9. ‘\r’: command not found – .bashrc / .bash_profile [duplicate]
  10. Bash: limit the number of concurrent jobs? [duplicate]
  11. Bash command to sum a column of numbers [duplicate]
  12. Why can’t I use job control in a bash script?
  13. Specify other flags in awk script header
  14. echo that outputs to stderr
  15. Bash if statement with multiple conditions throws an error
  16. How to show and update echo on same line
  17. Concatenating multiple text files into a single file in Bash
  18. Bash indirect variable referencing
  19. Simulate user input in bash script [closed]
  20. Forking / Multi-Threaded Processes | Bash
  21. Why is #!/usr/bin/env bash superior to #!/bin/bash?
  22. Bash shell Decimal to Binary base 2 conversion
  23. Checking host availability by using ping in bash scripts
  24. using jq to assign multiple output variables
  25. -bash: !”: event not found [closed]
  26. How to substitute quoted, multi-word strings as arguments?
  27. Why do my setuid root bash shell scripts not work?
  28. Reference to a bash variable whose name contains dot
  29. How to delete rows from a csv file based on a list values from another file?
  30. ‘which’ vs ‘command -v’ in Bash [duplicate]

Leave a Comment