Bash: What does “masking return values” mean?
shellcheck generated the following warning
SC2155: Declare and assign separately to avoid masking return
values
For this line of code
local key_value=$(echo "$current_line" | mawk '/.+=.+/ {print $1 }')
What does "masking return values" mean, and how does it pertain to the aforementioned warning?
bash shell-script shellcheck
asked 5 hours ago
InquisitorInquisitor
304
New contributor
Inquisitor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
shellcheck generated the following warning
SC2155: Declare and assign separately to avoid masking return
values
For this line of code
local key_value=$(echo "$current_line" | mawk '/.+=.+/ {print $1 }')
What does "masking return values" mean, and how does it pertain to the aforementioned warning?
bash shell-script shellcheck
asked 5 hours ago
InquisitorInquisitor
304
New contributor
Inquisitor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
shellcheck generated the following warning
SC2155: Declare and assign separately to avoid masking return
values
For this line of code
local key_value=$(echo "$current_line" | mawk '/.+=.+/ {print $1 }')
What does "masking return values" mean, and how does it pertain to the aforementioned warning?
bash shell-script shellcheck
asked 5 hours ago
InquisitorInquisitor
304
New contributor
Inquisitor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
shellcheck generated the following warning
SC2155: Declare and assign separately to avoid masking return
values
For this line of code
local key_value=$(echo "$current_line" | mawk '/.+=.+/ {print $1 }')
What does "masking return values" mean, and how does it pertain to the aforementioned warning?
bash shell-script shellcheck
bash shell-script shellcheck
asked 5 hours ago
InquisitorInquisitor
304
New contributor
Inquisitor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 hours ago
InquisitorInquisitor
304
New contributor
Inquisitor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 4 hours ago
Inquisitor
asked 5 hours ago
InquisitorInquisitor
304
New contributor
Inquisitor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 hours ago
InquisitorInquisitor
304
asked 5 hours ago
InquisitorInquisitor
304
304
New contributor
Inquisitor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Inquisitor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Inquisitor is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
When you declare a variable as either local or exported that in itself is a command that will return success or not.
$ var=$(false)
$ echo $?
1
$ export var=$(false)
$ echo $?
0
So if you wanted to act on the return value of your command (echo "$current_line" | mawk '/.+=.+/ {print $1 }'), you would be unable to since it's going to exit with 0 as long as the local declaration succeeds (which is almost always will).
In order to avoid this it suggests declaring separately and then assigning:
local key_value
key_value=$(echo "$current_line" | mawk '/.+=.+/ {print $1 }')
This is a shellcheck rule I frequently ignore and IMO is safe to ignore as long as you know you aren't trying to act on the return value of that variable declaration.
You can ignore it by adding the following to the top of your script (Below the hashbang of course):
# shellcheck disable=SC2155
answered 5 hours ago
Jesse_bJesse_b
13.4k23370
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Inquisitor is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506352%2fbash-what-does-masking-return-values-mean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
When you declare a variable as either local or exported that in itself is a command that will return success or not.
$ var=$(false)
$ echo $?
1
$ export var=$(false)
$ echo $?
0
So if you wanted to act on the return value of your command (echo "$current_line" | mawk '/.+=.+/ {print $1 }'), you would be unable to since it's going to exit with 0 as long as the local declaration succeeds (which is almost always will).
In order to avoid this it suggests declaring separately and then assigning:
local key_value
key_value=$(echo "$current_line" | mawk '/.+=.+/ {print $1 }')
This is a shellcheck rule I frequently ignore and IMO is safe to ignore as long as you know you aren't trying to act on the return value of that variable declaration.
You can ignore it by adding the following to the top of your script (Below the hashbang of course):
# shellcheck disable=SC2155
answered 5 hours ago
Jesse_bJesse_b
13.4k23370
add a comment |
When you declare a variable as either local or exported that in itself is a command that will return success or not.
$ var=$(false)
$ echo $?
1
$ export var=$(false)
$ echo $?
0
So if you wanted to act on the return value of your command (echo "$current_line" | mawk '/.+=.+/ {print $1 }'), you would be unable to since it's going to exit with 0 as long as the local declaration succeeds (which is almost always will).
In order to avoid this it suggests declaring separately and then assigning:
local key_value
key_value=$(echo "$current_line" | mawk '/.+=.+/ {print $1 }')
This is a shellcheck rule I frequently ignore and IMO is safe to ignore as long as you know you aren't trying to act on the return value of that variable declaration.
You can ignore it by adding the following to the top of your script (Below the hashbang of course):
# shellcheck disable=SC2155
answered 5 hours ago
Jesse_bJesse_b
13.4k23370
add a comment |
When you declare a variable as either local or exported that in itself is a command that will return success or not.
$ var=$(false)
$ echo $?
1
$ export var=$(false)
$ echo $?
0
So if you wanted to act on the return value of your command (echo "$current_line" | mawk '/.+=.+/ {print $1 }'), you would be unable to since it's going to exit with 0 as long as the local declaration succeeds (which is almost always will).
In order to avoid this it suggests declaring separately and then assigning:
local key_value
key_value=$(echo "$current_line" | mawk '/.+=.+/ {print $1 }')
This is a shellcheck rule I frequently ignore and IMO is safe to ignore as long as you know you aren't trying to act on the return value of that variable declaration.
You can ignore it by adding the following to the top of your script (Below the hashbang of course):
# shellcheck disable=SC2155
answered 5 hours ago
Jesse_bJesse_b
13.4k23370
When you declare a variable as either local or exported that in itself is a command that will return success or not.
$ var=$(false)
$ echo $?
1
$ export var=$(false)
$ echo $?
0
So if you wanted to act on the return value of your command (echo "$current_line" | mawk '/.+=.+/ {print $1 }'), you would be unable to since it's going to exit with 0 as long as the local declaration succeeds (which is almost always will).
In order to avoid this it suggests declaring separately and then assigning:
local key_value
key_value=$(echo "$current_line" | mawk '/.+=.+/ {print $1 }')
This is a shellcheck rule I frequently ignore and IMO is safe to ignore as long as you know you aren't trying to act on the return value of that variable declaration.
You can ignore it by adding the following to the top of your script (Below the hashbang of course):
# shellcheck disable=SC2155
answered 5 hours ago
Jesse_bJesse_b
13.4k23370
answered 5 hours ago
Jesse_bJesse_b
13.4k23370
answered 5 hours ago
Jesse_bJesse_b
13.4k23370
answered 5 hours ago
Jesse_bJesse_b
13.4k23370
13.4k23370
add a comment |
add a comment |
Inquisitor is a new contributor. Be nice, and check out our Code of Conduct.
Inquisitor is a new contributor. Be nice, and check out our Code of Conduct.
Inquisitor is a new contributor. Be nice, and check out our Code of Conduct.
Inquisitor is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506352%2fbash-what-does-masking-return-values-mean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
