Programming

17454 readers

142 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

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 [email protected]

founded 1 year ago

MODERATORS

[email protected]

POSIX.1-2024 has been published (ieeexplore.ieee.org)

submitted 5 months ago by [email protected] to c/[email protected]

14 comments fedilink hide all child comments

A note from earlier today says the HTML edition will be available soon. I assume that means it will show up here: https://pubs.opengroup.org/onlinepubs/9699919799/

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] -2 points 5 months ago* (last edited 5 months ago) (3 children)

Shell scripts were a mistake. The weirdness you have to remember to safely stop executing when something fails is mind-boggling.

I'm so glad nushell exists and doesn't need any configuring to just do the reasonable thing and stop executing when something fails.

[–] [email protected] 2 points 5 months ago* (last edited 5 months ago)

Shell scripts were a mistake.

I understand 1000% but I'm not sure I agree. With the peevishness of C and latent autism of assembly, something compiled or otherwise binary isn't always simple and straightforward. Sometimes, you have a task that only needs to be done three times, and just replaying the commands is sufficient.

sh, ash, and bash are all kinda dumb. Absolutely. But there are other shells that are significantly better. csh and zsh are both great. ksh has some history on it but is good too. But "shell scripts" don't have to be in your shell language. The hashbang line will let you make a command file and so long as you can describe the command line you can get most shells to run it. Be that language ~~line noise~~ perl or python or even go.

[–] [email protected] 1 points 5 months ago (1 children)

All you need to do is set -e at the start of the script to stop on a non-0 exit code. And quote variables to prevent globbing.

[–] [email protected] 0 points 5 months ago (1 children)

Oh you sweet summer child.

If you don't use pipes or command substitutions, set -e gets you a fair part of the way there.

If you're interested, I can look up the rest of the arcane incantations necessary.

[–] [email protected] 1 points 5 months ago* (last edited 5 months ago) (1 children)

Shell scripts were a mistake. The weirdness you have to remember to safely stop executing when something fails is mind-boggling.

nushell scripts aren't shellscripts?

[–] [email protected] 1 points 5 months ago

I usually write “POSIXy shell” but I thought that was clear from context this time.

The problem is that exit statuses !=0 aren't treated as error by default (with a way to turn that off for individual expressions). Instead you have to set multiple settings and avoid certain constructs in bash/ZSH/...

Everything that works like a modern programming language by default is fine of course