RubyGems - retry - Versions diffs - 0.0.1 → 0.0.2 - Mend

retry 0.0.1 → 0.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (7) hide show

data/README.txt CHANGED Viewed

@@ -9,10 +9,10 @@ The Retry gem easily allows you to wrap a block of text in a "retry" so that it
 Usage is relatively simple:
- 10.tries('doing work') do
+ 10.tries do
    # unreliable code goes here...
    raise 'network connection failed' if rand() < 0.7
    puts 'success'
  end
+For further options, see Fixnum#tries

data/Rakefile CHANGED Viewed

@@ -2,12 +2,15 @@ require 'rubygems'
 require 'rake'
 require 'rake/clean'
 require 'rake/testtask'
+require 'spec/rake/spectask'
 require 'rake/packagetask'
 require 'rake/gempackagetask'
 require 'rake/rdoctask'
 require 'rake/contrib/rubyforgepublisher'
 require 'fileutils'
 require 'hoe'
 include FileUtils
 require File.join(File.dirname(__FILE__), 'lib', 'retry', 'version')
@@ -91,3 +94,7 @@ task :check_version do
   end
 end
+desc "Run All Specs"
+Spec::Rake::SpecTask.new('spec') do |t|
+  t.spec_files = FileList['spec/**/*.rb']
+end

data/lib/retry.rb CHANGED Viewed

@@ -2,7 +2,12 @@ require 'retry/version'
 class Fixnum
-  def tries(message) # :yields:
+=begin rdoc
+- message       => allows you to provide some context to the error messages that get printed out.
+- output_stream =>  allows you to specify to which output stream you want any errors to be written.  Defaults to $stderr
+=end
+  def tries(message = nil, output_stream = $stderr) # :yields:
     current_try_num = 1
     begin
       yield current_try_num
@@ -10,7 +15,8 @@ class Fixnum
       if current_try_num >= self
         raise
       else
-        puts "Try #{current_try_num} failed (#{message}): #{e}"
+        m = message ? " (#{message})" : ''
+        output_stream.puts "Try #{current_try_num} failed#{m}: #{e}"
         current_try_num = current_try_num.next
         retry
       end

data/lib/retry/version.rb CHANGED Viewed

@@ -2,7 +2,7 @@ module Retry #:nodoc:
   module VERSION #:nodoc:
     MAJOR = 0
     MINOR = 0
-    TINY  = 1
+    TINY  = 2
     STRING = [MAJOR, MINOR, TINY].join('.')
   end

data/website/index.html CHANGED Viewed

@@ -5,7 +5,7 @@
   <link rel="stylesheet" href="stylesheets/screen.css" type="text/css" media="screen" />
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   <title>
-      retry
+      Retry Gem
   </title>
   <script src="javascripts/rounded_corners_lite.inc.js" type="text/javascript"></script>
 <style>
@@ -30,15 +30,15 @@
 <body>
 <div id="main">
-    <h1>retry</h1>
+    <h1>Retry Gem</h1>
     <div id="version" class="clickable" onclick='document.location = "http://rubyforge.org/projects/retry"; return false'>
       Get Version
-      <a href="http://rubyforge.org/projects/retry" class="numbers">0.0.1</a>
+      <a href="http://rubyforge.org/projects/retry" class="numbers">0.0.2</a>
     </div>
-    <h1>&#x2192; &#8216;retry&#8217;</h1>
+    <h2>What</h2>
-	<h2>What</h2>
+	<p>Benjamin Franklin said, &#8220;The definition of insanity is doing the same thing over and over and expecting different results.&#8221;  Sometimes, though, a retry is exactly what you need. You may need to call something that is not reliable. Maybe it is a network connection that might be down temporarily. How often have you built retry logic around a bit of code that just might fail on occasion? This ruby gem takes care of that situation nicely.</p>
 	<h2>Installing</h2>
@@ -46,20 +46,29 @@
 <pre syntax="ruby">sudo gem install retry</pre>
-	<h2>The basics</h2>
 	<h2>Demonstration of usage</h2>
-	<h2>Forum</h2>
+<pre syntax="ruby">
+require 'retry'
+10.tries do
+  raise 'network connection failed' if rand() &lt; 0.7
+  puts 'success'
+end
+</pre>
+	<p>Output:</p>
-	<p><a href="http://groups.google.com/group/retry">http://groups.google.com/group/retry</a></p>
+<pre syntax="ruby">
-	<p><span class="caps">TODO</span> &#8211; create Google Group &#8211; retry</p>
+&gt; ruby tries.rb
+&gt; Try 1 failed: network connection failed
+&gt; Try 2 failed: network connection failed
+&gt; success
+</pre>
 	<h2>License</h2>

data/website/index.txt CHANGED Viewed

@@ -1,27 +1,35 @@
-h1. retry
-h1. &#x2192; 'retry'
+h1. Retry Gem
 h2. What
+Benjamin Franklin said, "The definition of insanity is doing the same thing over and over and expecting different results."  Sometimes, though, a retry is exactly what you need. You may need to call something that is not reliable. Maybe it is a network connection that might be down temporarily. How often have you built retry logic around a bit of code that just might fail on occasion? This ruby gem takes care of that situation nicely.
 h2. Installing
 <pre syntax="ruby">sudo gem install retry</pre>
-h2. The basics
 h2. Demonstration of usage
+<pre syntax="ruby">
+require 'retry'
+10.tries do
+  raise 'network connection failed' if rand() < 0.7
+  puts 'success'
+end
+</pre>
+Output:
-h2. Forum
+<pre syntax="ruby">
-"http://groups.google.com/group/retry":http://groups.google.com/group/retry
+> ruby tries.rb
+> Try 1 failed: network connection failed
+> Try 2 failed: network connection failed
+> success
-TODO - create Google Group - retry
+</pre>
 h2. License

metadata CHANGED Viewed

@@ -3,7 +3,7 @@ rubygems_version: 0.9.0
 specification_version: 1
 name: retry
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
 date: 2007-06-01 00:00:00 +01:00
 summary: easily retry blocks of code
 require_paths: