Bash: What does “masking return values” mean?2019 Community Moderator ElectionHow to name a file in the...

Why must traveling waves have the same amplitude to form a standing wave?

Why is a Java array index expression evaluated before checking if the array reference expression is null?

I need to drive a 7/16" nut but am unsure how to use the socket I bought for my screwdriver

What is the greatest age difference between a married couple in Tanach?

How to simplify this time periods definition interface?

Why did it take so long to abandon sail after steamships were demonstrated?

Citation at the bottom for subfigures in beamer frame

Be in awe of my brilliance!

Font with correct density?

Possible Leak In Concrete

Fill color and outline color with the same value

Rejected in 4th interview round citing insufficient years of experience

Russian cases: A few examples, I'm really confused

Pinhole Camera with Instant Film

Is it true that real estate prices mainly go up?

The use of "touch" and "touch on" in context

My story is written in English, but is set in my home country. What language should I use for the dialogue?

Did CPM support custom hardware using device drivers?

Making a sword in the stone, in a medieval world without magic

How to get the name of the database a stored procedure is executed in within that stored procedure while it's executing?

Co-worker team leader wants to inject his friend's awful software into our development. What should I say to our common boss?

Why do Australian milk farmers need to protest supermarkets' milk price?

Does this AnyDice function accurately calculate the number of ogres you make unconcious with three 4th-level castings of Sleep?

Provisioning profile doesn't include the application-identifier and keychain-access-groups entitlements



Bash: What does “masking return values” mean?



2019 Community Moderator ElectionHow to name a file in the deepest level of a directory treeWhat does || mean in bash?Printf formatting with variable format - what does this var reference?What does $'r' mean?What is return code 1 for git-rebase? What are other values it could return?How does one parse ${!i} (and what does it mean)?Should I double quote these parameter expansions?“Make sure not to read and write the same file in the same pipeline”How to return a values from a method which prints its out putWhy not to export variables on the same line you assign them?












5















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?










share|improve this question









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.

























    5















    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?










    share|improve this question









    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.























      5












      5








      5








      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?










      share|improve this question









      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






      share|improve this question









      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.











      share|improve this question









      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.









      share|improve this question




      share|improve this question








      edited 53 mins ago







      Inquisitor













      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 1 hour 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.






















          1 Answer
          1






          active

          oldest

          votes


















          5














          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





          share|improve this answer























            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.










            draft saved

            draft discarded


















            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









            5














            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





            share|improve this answer




























              5














              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





              share|improve this answer


























                5












                5








                5







                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





                share|improve this answer













                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






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 1 hour ago









                Jesse_bJesse_b

                13.4k23370




                13.4k23370






















                    Inquisitor is a new contributor. Be nice, and check out our Code of Conduct.










                    draft saved

                    draft discarded


















                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    Gersau Kjelder | Navigasjonsmeny46°59′0″N 8°31′0″E46°59′0″N...

                    Nässjö kommun Tettstader | Kjelder | NavigasjonsmenyeVIAFISNIGeoNamesMusicBrainz (area)

                    Kvitkval Innhaldsliste Taksonomi og utvikling | Utsjånad og levevis | Utbreiing | Åtferd |...