Ruby: what is correct way to print to the console (puts or print_info)?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I tried both approaches and both print to the console.



puts "Hello World"



print_info "Hello World"


What is the real difference between them and which approach is better than another?






ruby printing console







share|improve this question





























    0















    I tried both approaches and both print to the console.



    puts "Hello World"
    

    
print_info "Hello World"


    What is the real difference between them and which approach is better than another?






    ruby printing console







    share|improve this question

























      0












      0








      0








      I tried both approaches and both print to the console.



      puts "Hello World"
      

      
print_info "Hello World"


      What is the real difference between them and which approach is better than another?






      ruby printing console







      share|improve this question














      I tried both approaches and both print to the console.



      puts "Hello World"
      

      
print_info "Hello World"


      What is the real difference between them and which approach is better than another?






      ruby printing console




      ruby printing console






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 3 at 20:24









      TiredOfProgrammingTiredOfProgramming

      360316




      360316
























          1 Answer
          1






          active

          oldest

          votes


















          3














          To start print_info is not standard ruby. Could be a rails thing? I dunno.



          Now two actual choices puts vs p



          puts outputs data using to_s to convert to strings. It has a special case for arrays, putting each array element on its own line. It returns nil



          p outputs data using inspect to convert to strings. It has no special case for arrays. It returns its arguments singly if there is only one or in an array if there is more than one.



          Which is better? It depends if you want to_s or inspect. I find that p is useful in debugging situations as it can "peek" at values without needing special debug code.



          For example the code:



          result = my_object.my_method(arg1, arg2)


          can be instrumented as:



          result = p my_object.my_method(p(arg1), p(arg2))


          All things said though puts is more popular, so that is what I normally use.



          Also don't forget pp which is pretty print, that prints out data in a more meaningful way. Before Ruby 2.6 you'll need to remember to:



          require 'pp'





          share|improve this answer



















          • 1





            It's definitely not a Rails thing either. Not sure where OP got that command.

            – anothermh
            Jan 4 at 1:50












          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2fstackoverflow.com%2fquestions%2f54029299%2fruby-what-is-correct-way-to-print-to-the-console-puts-or-print-info%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














          To start print_info is not standard ruby. Could be a rails thing? I dunno.



          Now two actual choices puts vs p



          puts outputs data using to_s to convert to strings. It has a special case for arrays, putting each array element on its own line. It returns nil



          p outputs data using inspect to convert to strings. It has no special case for arrays. It returns its arguments singly if there is only one or in an array if there is more than one.



          Which is better? It depends if you want to_s or inspect. I find that p is useful in debugging situations as it can "peek" at values without needing special debug code.



          For example the code:



          result = my_object.my_method(arg1, arg2)


          can be instrumented as:



          result = p my_object.my_method(p(arg1), p(arg2))


          All things said though puts is more popular, so that is what I normally use.



          Also don't forget pp which is pretty print, that prints out data in a more meaningful way. Before Ruby 2.6 you'll need to remember to:



          require 'pp'





          share|improve this answer



















          • 1





            It's definitely not a Rails thing either. Not sure where OP got that command.

            – anothermh
            Jan 4 at 1:50
















          3














          To start print_info is not standard ruby. Could be a rails thing? I dunno.



          Now two actual choices puts vs p



          puts outputs data using to_s to convert to strings. It has a special case for arrays, putting each array element on its own line. It returns nil



          p outputs data using inspect to convert to strings. It has no special case for arrays. It returns its arguments singly if there is only one or in an array if there is more than one.



          Which is better? It depends if you want to_s or inspect. I find that p is useful in debugging situations as it can "peek" at values without needing special debug code.



          For example the code:



          result = my_object.my_method(arg1, arg2)


          can be instrumented as:



          result = p my_object.my_method(p(arg1), p(arg2))


          All things said though puts is more popular, so that is what I normally use.



          Also don't forget pp which is pretty print, that prints out data in a more meaningful way. Before Ruby 2.6 you'll need to remember to:



          require 'pp'





          share|improve this answer



















          • 1





            It's definitely not a Rails thing either. Not sure where OP got that command.

            – anothermh
            Jan 4 at 1:50














          3












          3








          3







          To start print_info is not standard ruby. Could be a rails thing? I dunno.



          Now two actual choices puts vs p



          puts outputs data using to_s to convert to strings. It has a special case for arrays, putting each array element on its own line. It returns nil



          p outputs data using inspect to convert to strings. It has no special case for arrays. It returns its arguments singly if there is only one or in an array if there is more than one.



          Which is better? It depends if you want to_s or inspect. I find that p is useful in debugging situations as it can "peek" at values without needing special debug code.



          For example the code:



          result = my_object.my_method(arg1, arg2)


          can be instrumented as:



          result = p my_object.my_method(p(arg1), p(arg2))


          All things said though puts is more popular, so that is what I normally use.



          Also don't forget pp which is pretty print, that prints out data in a more meaningful way. Before Ruby 2.6 you'll need to remember to:



          require 'pp'





          share|improve this answer













          To start print_info is not standard ruby. Could be a rails thing? I dunno.



          Now two actual choices puts vs p



          puts outputs data using to_s to convert to strings. It has a special case for arrays, putting each array element on its own line. It returns nil



          p outputs data using inspect to convert to strings. It has no special case for arrays. It returns its arguments singly if there is only one or in an array if there is more than one.



          Which is better? It depends if you want to_s or inspect. I find that p is useful in debugging situations as it can "peek" at values without needing special debug code.



          For example the code:



          result = my_object.my_method(arg1, arg2)


          can be instrumented as:



          result = p my_object.my_method(p(arg1), p(arg2))


          All things said though puts is more popular, so that is what I normally use.



          Also don't forget pp which is pretty print, that prints out data in a more meaningful way. Before Ruby 2.6 you'll need to remember to:



          require 'pp'






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 3 at 21:02









          Peter CamilleriPeter Camilleri

          1,5221217




          1,5221217








          • 1





            It's definitely not a Rails thing either. Not sure where OP got that command.

            – anothermh
            Jan 4 at 1:50














          • 1





            It's definitely not a Rails thing either. Not sure where OP got that command.

            – anothermh
            Jan 4 at 1:50








          1




          1





          It's definitely not a Rails thing either. Not sure where OP got that command.

          – anothermh
          Jan 4 at 1:50





          It's definitely not a Rails thing either. Not sure where OP got that command.

          – anothermh
          Jan 4 at 1:50




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • 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%2fstackoverflow.com%2fquestions%2f54029299%2fruby-what-is-correct-way-to-print-to-the-console-puts-or-print-info%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

          Monofisismo

          Image
          Monofisismo (do grego: monos - "único, singular" e physis - "natureza") é o ponto de vista cristológico que defende que, depois da união do divino e do humano na encarnação histórica, Jesus Cristo, como encarnação do Filho ou Verbo ( Logos ) de Deus, teria apenas uma única "natureza", a divina, e não uma síntese de ambas. O monofisismo é contraposto pelo diofisismo (ou "diafisismo"), que defende que Jesus preservou em si as duas naturezas. Historicamente, o monofisismo se refere primordialmente à posição dos que (especialmente no Egito e, em menor grau, na Síria) rejeitaram as decisões do Concílio de Calcedônia em 451 (o quarto concílio ecumênico). Os membros mais moderados entre eles, porém, defendem a teologia "miafisita", que se tornou a oficial para as Igrejas Ortodoxas Orientais. Muitos ortodoxos orientais, porém, rejeitam essa classificação, mesmo como um termo genérico, mas ele é amplamente utilizado na literatura históri...
          Read more

          Angular Downloading a file using contenturl with Basic Authentication

          Image
          0 I have a contentUrl when user clicks on that,file should be downloaded. If I try to browse the contentUrl in the browser it asks for Userid and password.I believe this is Basic Authentication.I dont want user to enter UserId and Password so I am passing it Authorization(Please see below code). Url looks some thing like this: http://XXX.XXX.XX.XXX:8080/flowable-rest/service/runtime/tasks/90875/attachments/90555/content let username : string = 'admin'; let pwd : string = 'test'; let headers = new Headers(); headers.set('Accept', 'text/json'); headers.append('Content-Type', 'application/json'); headers.set('Access-Control-Allow-Origin', '*'); headers.set('Access-Control-Allow-Methods','POST, GET, OPTIONS, PUT, DELETE'); head...
          Read more

          Olmecas

          Image
          Monumento 1, uma das quatro cabeças colossais encontradas em La Venta, com altura aproximada de 3 metros Olmecas é a designação do povo e da civilização que estiveram na origem da antiga cultura pré-colombiana da Mesoamérica e que se desenvolveram nas regiões tropicais do centro-sul do atual México durante o pré-clássico, próximo de onde hoje estão localizados os estados mexicanos de Veracruz e Tabasco, no Istmo de Tehuantepec, numa zona designada área nuclear olmeca. A cultura olmeca floresceu nesta região aproximadamente entre 1500 e 400 a.C., [ 1 ] e crê-se que tenha sido a civilização-mãe de todas as civilizações mesoamericanas que se desenvolveram posteriormente. [ 2 ] No entanto, desconhece-se a sua exacta filiação étnica, ainda que existam numerosas hipóteses colocadas para tentar resolver esta questão. O etnónimo olmeca foi cunhado pelos arqueólogos do século XX, e não devem confundir-se com os muito posteriores olmecas-xicalancas que ocuparam vários locais do México...
          Read more