Command Substitution: Can you return data instead of exit codes in Bash?

No video

Command Substitution: Can you return data instead of exit codes in Bash? | #3 Practical Bash

Рет қаралды 10,904

Күн бұрын

It seems bash only allows us to return an exit code from a function and not data like in other programming languages? So what do we instead? Can command substitution come to the rescue? In this video you'll learn how to safely pass data from one function in your script to another

Пікірлер: 14

@bernhardkern629 4 жыл бұрын

yay, my first youtube comment, just to tell you that your video series is great. Watched the https/tls video and landed in your bash series.

@kubucation 4 жыл бұрын

Thanks! I feel honored to receive your first ever youtube comment :-)

@ernestogutierrez7877 3 жыл бұрын

Had I known function return statements where meant for returning exit codes (0-255) back when I started coding bash scripts, I would have saved myself a lot of troubleshooting time :S Great video mate!

@soufianta8374 Жыл бұрын

Hi, this is one of the weird things I took time to understand. Actually, bash shouldn’t be compared to other languages (data types). Bash was supposed to run external binaries/commands that do their stuff and binaries don’t need to play with return values of other binaires. Nice video btw

@mithunmanoharmithun 4 жыл бұрын

This series is awesome. Thanks !

@jamesw6949 4 жыл бұрын

Introduced me to shellcheck, thanks!

@kubucation 4 жыл бұрын

And you just gave me the idea to create a video about shellcheck. Thanks :)

@jamesw6949 4 жыл бұрын

@@kubucation :)

@blank-vw2sb 2 жыл бұрын

Love the series. Thanks!!

@VoltVandal 5 жыл бұрын

thanks, very understandable

@kubucation 5 жыл бұрын

thanks a lot, very glad to hear :)

@loveanimals-0197 4 жыл бұрын

What if you had multiple echo statements within that called function?

@kubucation 4 жыл бұрын

All output that is usually sent to stdout would be caught. A single or multiple echo statements don't make a difference. We only see an echo statement as a "unit" because it automatically appends a new line ( ) at the end of the line. However, that's just a default setting and you can in fact not add a new line by using "echo -n foo". Similarly the new line would just be caught by the command substitution along with the remaining output.