this post was submitted on 26 Aug 2023
50 points (94.6% liked)

Programming

17326 readers
150 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] gamma@programming.dev 1 points 1 year ago (2 children)

This has never stuck with me, and I hadn't thought about why until now. I have two reasons why I will always write ${x}_$y.z instead of ${x}_${y}.z:

  • Syntax highlighting and shellcheck have always caught the cases I need to add braces to prevent $x_ being expanded as ${x_}.
  • I write a lot of Zsh. In Zsh, braces are optional in way more cases. "$#array[3]" actually prints the length of the third item in array, rather than (Bash:) the number of positional parameters, then the string 'array[3]'.
[–] thingsiplay@kbin.social 3 points 1 year ago

@gamma I just use them out of consistency and principle, so I don't need to think in which case it is required or not.

[–] cyclohexane@lemmy.ml 0 points 1 year ago

I will always write ${x}_$y.z instead of ${x}_${y}.z:

The difference between the two seems different to what's in the OP. Is there a typo here?