Comments on: Capture standard output in Ruby http://stefankst.net/2007/06/05/capture-standard-output-in-ruby/ Weblog Tue, 06 Jan 2009 22:59:41 +0000 http://wordpress.org/?v=2.3.3 By: Lancer Kind http://stefankst.net/2007/06/05/capture-standard-output-in-ruby/#comment-382 Lancer Kind Tue, 19 Feb 2008 19:57:06 +0000 http://stefankst.net/2007/06/05/capture-standard-output-in-ruby/#comment-382 Great article! This outlines a solution that goes a long way into solving unit testing of stdout that is a problem with Java/C#. It's also great that based on the need you've set up for code reuse, you introduced blocks/yield. The problem around StringIO not working is interesting. I agree with your conclusion about the code not using duck typing. Duck typing is something new that a lot of us are going to need to work at to get used to. Checking the type of the superclass in order to make decisions about its capabilities feels like the developer was still stuck in the strong type checking paradigm in Java/C#. When Java was the new cool OO kid on the block in 1995, one saw a lot of Java code that was written as if it was C (poor encapsulation, lots of public fields, few/really-long methods, checking return codes instead of using exception handling). I expect a lot of Ruby code is going to look like Java/C# code but implemented in Ruby for a while until people unlearn some habits. (I know I'm working to do that.) Bravo! Reading this has been a great use of my time! Great article! This outlines a solution that goes a long way into solving unit testing of stdout that is a problem with Java/C#. It’s also great that based on the need you’ve set up for code reuse, you introduced blocks/yield.

The problem around StringIO not working is interesting. I agree with your conclusion about the code not using duck typing. Duck typing is something new that a lot of us are going to need to work at to get used to. Checking the type of the superclass in order to make decisions about its capabilities feels like the developer was still stuck in the strong type checking paradigm in Java/C#. When Java was the new cool OO kid on the block in 1995, one saw a lot of Java code that was written as if it was C (poor encapsulation, lots of public fields, few/really-long methods, checking return codes instead of using exception handling). I expect a lot of Ruby code is going to look like Java/C# code but implemented in Ruby for a while until people unlearn some habits. (I know I’m working to do that.)

Bravo! Reading this has been a great use of my time!

]]> By: Nick http://stefankst.net/2007/06/05/capture-standard-output-in-ruby/#comment-9 Nick Fri, 21 Sep 2007 18:24:44 +0000 http://stefankst.net/2007/06/05/capture-standard-output-in-ruby/#comment-9 This rocks. I wrote a couple of scripts to check on mysql replication. The scripts write to a log file and stardard out, but I want to send a daily report on the replication, and this should make it easy to capture the output from the script and stick it in an email. Thanks This rocks. I wrote a couple of scripts to check on mysql replication. The scripts write to a log file and stardard out, but I want to send a daily report on the replication, and this should make it easy to capture the output from the script and stick it in an email. Thanks

]]>