Perl - Why I can't use a variable into regex?












1















Why can't I use if($l =~ $ARGV[0]) but I can use if($l =~ /$ARGV[0]/g?



first case

$ perl script.pl '/^[w]/g'


second case

$ perl script.pl '^[w]'









share|improve this question





























    1















    Why can't I use if($l =~ $ARGV[0]) but I can use if($l =~ /$ARGV[0]/g?



    first case

    $ perl script.pl '/^[w]/g'


    second case

    $ perl script.pl '^[w]'









    share|improve this question



























      1












      1








      1








      Why can't I use if($l =~ $ARGV[0]) but I can use if($l =~ /$ARGV[0]/g?



      first case

      $ perl script.pl '/^[w]/g'


      second case

      $ perl script.pl '^[w]'









      share|improve this question
















      Why can't I use if($l =~ $ARGV[0]) but I can use if($l =~ /$ARGV[0]/g?



      first case

      $ perl script.pl '/^[w]/g'


      second case

      $ perl script.pl '^[w]'






      perl






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 17 mins ago









      Rui F Ribeiro

      40.1k1479136




      40.1k1479136










      asked Dec 13 '15 at 16:50









      The dudeThe dude

      1259




      1259






















          1 Answer
          1






          active

          oldest

          votes


















          3














          $ARGV[0] is a scalar string. When you do if($l =~ $ARGV[0]) and $ARGV[0] is '/^[w]/g' this is equivalent to if($l =~ '/^[w]/g') instead of if($l =~ /^[w]/g). In the former case the slashes are simply characters in a string while in the later they are a part of the Perl syntax that delimits a regular expression.






          share|improve this answer





















          • 2





            To work around this, you can use $regex = qr{$ARGV [0]}

            – Joseph R.
            Dec 13 '15 at 20:03













          • Hey, thanks for the advice guys. Could you take a look at this question mentioning other error in the same script? unix.stackexchange.com/questions/249368/…

            – The dude
            Dec 14 '15 at 21:08













          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
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f249105%2fperl-why-i-cant-use-a-variable-into-regex%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









          3














          $ARGV[0] is a scalar string. When you do if($l =~ $ARGV[0]) and $ARGV[0] is '/^[w]/g' this is equivalent to if($l =~ '/^[w]/g') instead of if($l =~ /^[w]/g). In the former case the slashes are simply characters in a string while in the later they are a part of the Perl syntax that delimits a regular expression.






          share|improve this answer





















          • 2





            To work around this, you can use $regex = qr{$ARGV [0]}

            – Joseph R.
            Dec 13 '15 at 20:03













          • Hey, thanks for the advice guys. Could you take a look at this question mentioning other error in the same script? unix.stackexchange.com/questions/249368/…

            – The dude
            Dec 14 '15 at 21:08


















          3














          $ARGV[0] is a scalar string. When you do if($l =~ $ARGV[0]) and $ARGV[0] is '/^[w]/g' this is equivalent to if($l =~ '/^[w]/g') instead of if($l =~ /^[w]/g). In the former case the slashes are simply characters in a string while in the later they are a part of the Perl syntax that delimits a regular expression.






          share|improve this answer





















          • 2





            To work around this, you can use $regex = qr{$ARGV [0]}

            – Joseph R.
            Dec 13 '15 at 20:03













          • Hey, thanks for the advice guys. Could you take a look at this question mentioning other error in the same script? unix.stackexchange.com/questions/249368/…

            – The dude
            Dec 14 '15 at 21:08
















          3












          3








          3







          $ARGV[0] is a scalar string. When you do if($l =~ $ARGV[0]) and $ARGV[0] is '/^[w]/g' this is equivalent to if($l =~ '/^[w]/g') instead of if($l =~ /^[w]/g). In the former case the slashes are simply characters in a string while in the later they are a part of the Perl syntax that delimits a regular expression.






          share|improve this answer















          $ARGV[0] is a scalar string. When you do if($l =~ $ARGV[0]) and $ARGV[0] is '/^[w]/g' this is equivalent to if($l =~ '/^[w]/g') instead of if($l =~ /^[w]/g). In the former case the slashes are simply characters in a string while in the later they are a part of the Perl syntax that delimits a regular expression.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Dec 13 '15 at 17:34

























          answered Dec 13 '15 at 17:26









          nwknwk

          663513




          663513








          • 2





            To work around this, you can use $regex = qr{$ARGV [0]}

            – Joseph R.
            Dec 13 '15 at 20:03













          • Hey, thanks for the advice guys. Could you take a look at this question mentioning other error in the same script? unix.stackexchange.com/questions/249368/…

            – The dude
            Dec 14 '15 at 21:08
















          • 2





            To work around this, you can use $regex = qr{$ARGV [0]}

            – Joseph R.
            Dec 13 '15 at 20:03













          • Hey, thanks for the advice guys. Could you take a look at this question mentioning other error in the same script? unix.stackexchange.com/questions/249368/…

            – The dude
            Dec 14 '15 at 21:08










          2




          2





          To work around this, you can use $regex = qr{$ARGV [0]}

          – Joseph R.
          Dec 13 '15 at 20:03







          To work around this, you can use $regex = qr{$ARGV [0]}

          – Joseph R.
          Dec 13 '15 at 20:03















          Hey, thanks for the advice guys. Could you take a look at this question mentioning other error in the same script? unix.stackexchange.com/questions/249368/…

          – The dude
          Dec 14 '15 at 21:08







          Hey, thanks for the advice guys. Could you take a look at this question mentioning other error in the same script? unix.stackexchange.com/questions/249368/…

          – The dude
          Dec 14 '15 at 21:08




















          draft saved

          draft discarded




















































          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%2f249105%2fperl-why-i-cant-use-a-variable-into-regex%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

          CARDNET

          Boot-repair Failure: Unable to locate package grub-common:i386

          濃尾地震