See the following examples and their outputs in POSIX shells:false;echo $? or false || echo 1: 1false;foo=bar;echo $? or foo=bar && echo 0: 0foo=$(false);echo $? or foo=$(false) || echo 1: 1foo=$(true);echo $? or foo=$(true) && echo 0: 0As mentioned by the highest-voted answer at https://stackoverflow.com/questions/6834487/what-is-the-variable-in-shell-scripting:$? is used to find the return value of the last executed command.This is probably a bit misleading in this case, so let's get the POSIX definition which is also quoted in a post from that thread:? Expands to the decimal exit status of the most recent pipeline (see Pipelines).So it appears as if a assignment itself counts as a command (or rather a pipeline part) with a zero exit value but which applies before the right side of the assignment (e.g. the command substitution calls in my examples here).I see how this behavior makes sense from a practical standpoint but it seems somewhat unusual to me that the assignment itself would count in that order. Maybe to make more clear why it's strange to me, let's assume the assignment was a function:ASSIGNMENT( VARIABLE, VALUE )then foo=bar would beASSIGNMENT( foo, bar )and foo=$(false) would be something likeASSIGNMENT( foo, EXECUTE( false ) )which would mean that EXECUTE runs first and only afterwards ASSIGNMENT is run but it's still the EXECUTE status that matters here.Am I correct in my assessment or am I misunderstanding/missing something?Are those the right reasons for me viewing this behavior as strange?
Assignments are like commands with an exit status except when there's command substitution?
shell;posix;command substitution;return status;assignment
The exit status for assignments is strange. The most obvious way for an assignment to fail is if the target variable is marked readonly.$ err(){ echo error ; return ${1:-1} ; }$ PS1='$? $ '0 $ err 42error42 $ A=$(err 12)12 $ if A=$(err 9) ; then echo wrong ; else E=$? ; echo E=$E ?=$? ; fiE=9 ?=00 $ readonly A0 $ if A=$(err 10) ; then echo wrong ; else E=$? ; echo E=$E ?=$? ; fiA: is read only1 $Note that neither the true nor false paths of the if statement were taken, the assignment failing stopped execution of the entire statement. bash in POSIX mode and ksh93 and zsh will all abort a script if an assignment fails.To quote the POSIX standard on this:A command without a command name, but one that includes a command substitution, has an exit status of the last command substitution that the shell performed.This is exactly the part of the shell grammar involved in foo=$(err 42)which comes from a simple_command (simple_command  cmd_prefix  ASSIGNMENT_WORD). So if an assignment succeeds then the exit status is zero unless command substitution was involved, in which case the exit status is the status of the last one. If the assignment fails then the exit status is non-zero, but you may not be able to catch it. 