atomic 1.1.2 → 1.1.3

data/{README.md → README.rdoc}

@@ -1,7 +1,6 @@
-atomic: An atomic reference implementation for JRuby, Rubinius, and MRI.
+= An atomic reference implementation for JRuby, Rubinius, and MRI.
 
-Summary
-=======
+== Summary
 
 This library provides:
 
@@ -20,8 +19,8 @@ methods:
 
 The atomic repository is at http://github.com/headius/ruby-atomic.
 
-Usage
-=====
+
+== Usage
 
 The simplest way to use "atomic" is to call the "update" or "try_update"
 methods.
@@ -57,8 +56,7 @@ my_atomic.compare_and_swap(2, 3) # => true, updated to 3
 my_atomic.compare_and_swap(2, 3) # => false, current is not 2
 ````
 
-Building
-========
+== Building
 
 As of 1.1.0, JDK8 is required to build the atomic gem, since it attempts to use
 the new atomic Unsafe.getAndSetObject method only in JDK8. The resulting code

data/atomic.gemspec

@@ -1,21 +1,25 @@
 # -*- encoding: utf-8 -*-
 
 # Update these to get proper version and commit history
-new_version = "1.1.2"
-old_version = "1.1.1"
+new_version = "1.1.3"
+old_version = "1.1.0"
+
+lines = File.readlines("README.rdoc")
+description = <<EOS
+#{lines[0]}
+
+== Changes since #{old_version}
+
+#{`git log --oneline #{old_version}...#{new_version}`}
+#{lines[0..-1].join("\n")}
+EOS
 
 Gem::Specification.new do |s|
   s.name = %q{atomic}
   s.version = new_version
   s.authors = ["Charles Oliver Nutter", "MenTaLguY", "Sokolov Yura"]
   s.date = Time.now.strftime('%Y-%m-%d')
-  s.description = <<EOS
-Changes in version #{new_version}:
-
-#{`git log --oneline #{old_version}...#{new_version}`}
-#{`kramdown README.md`}
-EOS
-puts s.description
+  s.description = description
   s.email = ["headius@headius.com", "mental@rydia.net", "funny.falcon@gmail.com"]
   s.homepage = "http://github.com/headius/ruby-atomic"
   s.require_paths = ["lib"]

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: atomic
 version: !ruby/object:Gem::Version
-  version: 1.1.2
+  version: 1.1.3
   prerelease: 
 platform: ruby
 authors:
@@ -13,35 +13,40 @@ bindir: bin
 cert_chain: []
 date: 2013-04-05 00:00:00.000000000 Z
 dependencies: []
-description: ! "Changes in version 1.1.2:\n\nf519385 Attempting to get description
-  to look nice on rubygems.org.\n\n<p>atomic: An atomic reference implementation for
-  JRuby, Rubinius, and MRI.</p>\n\n<h1 id=\"summary\">Summary</h1>\n\n<p>This library
-  provides:</p>\n\n<ul>\n  <li>an Atomic class that guarantees atomic updates to its
-  contained value</li>\n</ul>\n\n<p>The Atomic class provides accessors for the contained
-  “value” plus two update\nmethods:</p>\n\n<ul>\n  <li>update will run the provided
-  block, passing the current value and replacing\nit with the block result iff the
-  value has not been changed in the mean time.\nIt may run the block repeatedly if
-  there are other concurrent updates in\nprogress.</li>\n  <li>try_update will run
-  the provided block, passing the current value and\nreplacing it with the block result.
-  If the value changes before the update\ncan happen, it will throw Atomic::ConcurrentUpdateError.</li>\n</ul>\n\n<p>The
-  atomic repository is at http://github.com/headius/ruby-atomic.</p>\n\n<h1 id=\"usage\">Usage</h1>\n\n<p>The
-  simplest way to use “atomic” is to call the “update” or “try_update”\nmethods.</p>\n\n<p>“try_update”
-  and “update” both call the given block, passing the current\nvalue and using the
-  block’s result as the new value. If the value is updated\nby another thread before
-  the block completes, “try update” raises a\nConcurrentUpdateError and “update” retries
-  the block. Because “update” may call\nthe block several times when multiple threads
-  are all updating the same value,\nthe block’s logic should be kept as simple as
-  possible.</p>\n\n<p>````ruby\nrequire ‘atomic’</p>\n\n<p>my_atomic = Atomic.new(0)\nmy_atomic.update
-  {|v| v + 1}\nbegin\n  my_atomic.try_update {|v| v + 1}\nrescue Atomic::ConcurrentUpdateError
-  =&gt; cue\n  # deal with it (retry, propagate, etc)\nend\n````</p>\n\n<p>It’s also
-  possible to use the regular get/set operations on the Atomic, if you\nwant to avoid
-  the exception and respond to contended changes in some other way.</p>\n\n<p><code>ruby\nmy_atomic
-  = Atomic.new(0)\nmy_atomic.value # =&gt; 0\nmy_atomic.value = 1\nmy_atomic.swap(2)
-  # =&gt; 1\nmy_atomic.compare_and_swap(2, 3) # =&gt; true, updated to 3\nmy_atomic.compare_and_swap(2,
-  3) # =&gt; false, current is not 2\n</code></p>\n\n<h1 id=\"building\">Building</h1>\n\n<p>As
-  of 1.1.0, JDK8 is required to build the atomic gem, since it attempts to use\nthe
-  new atomic Unsafe.getAndSetObject method only in JDK8. The resulting code\nshould
-  still work fine as far back as Java 5.</p>\n\n"
+description: ! "= An atomic reference implementation for JRuby, Rubinius, and MRI.\n\n\n==
+  Changes since 1.1.0\n\n58d3e34 Convert README to rdoc and try again.\nf519385 Attempting
+  to get description to look nice on rubygems.org.\n2c5ab6c Include README and oneline
+  logs in gem description.\n6aeb053 Add @funny-falcon to authors.\naa24d4d Bump version
+  to 1.1.1.\ndc327eb Merge pull request #16 from funny-falcon/patch-1\n1b68767 Fix
+  JRUBYREFERENCE8_ALLOCATOR\n\n= An atomic reference implementation for JRuby, Rubinius,
+  and MRI.\n\n\n\n== Summary\n\n\n\nThis library provides:\n\n\n\n* an Atomic class
+  that guarantees atomic updates to its contained value\n\n\n\nThe Atomic class provides
+  accessors for the contained \"value\" plus two update\n\nmethods:\n\n\n\n* update
+  will run the provided block, passing the current value and replacing\n\n  it with
+  the block result iff the value has not been changed in the mean time.\n\n  It may
+  run the block repeatedly if there are other concurrent updates in\n\n  progress.\n\n*
+  try_update will run the provided block, passing the current value and\n\n  replacing
+  it with the block result. If the value changes before the update\n\n  can happen,
+  it will throw Atomic::ConcurrentUpdateError.\n\n\n\nThe atomic repository is at
+  http://github.com/headius/ruby-atomic.\n\n\n\n\n\n== Usage\n\n\n\nThe simplest way
+  to use \"atomic\" is to call the \"update\" or \"try_update\"\n\nmethods.\n\n\n\n\"try_update\"
+  and \"update\" both call the given block, passing the current\n\nvalue and using
+  the block's result as the new value. If the value is updated\n\nby another thread
+  before the block completes, \"try update\" raises a\n\nConcurrentUpdateError and
+  \"update\" retries the block. Because \"update\" may call\n\nthe block several times
+  when multiple threads are all updating the same value,\n\nthe block's logic should
+  be kept as simple as possible.\n\n\n\n````ruby\n\nrequire 'atomic'\n\n\n\nmy_atomic
+  = Atomic.new(0)\n\nmy_atomic.update {|v| v + 1}\n\nbegin\n\n  my_atomic.try_update
+  {|v| v + 1}\n\nrescue Atomic::ConcurrentUpdateError => cue\n\n  # deal with it (retry,
+  propagate, etc)\n\nend\n\n````\n\n\n\nIt's also possible to use the regular get/set
+  operations on the Atomic, if you\n\nwant to avoid the exception and respond to contended
+  changes in some other way.\n\n\n\n````ruby\n\nmy_atomic = Atomic.new(0)\n\nmy_atomic.value
+  # => 0\n\nmy_atomic.value = 1\n\nmy_atomic.swap(2) # => 1\n\nmy_atomic.compare_and_swap(2,
+  3) # => true, updated to 3\n\nmy_atomic.compare_and_swap(2, 3) # => false, current
+  is not 2\n\n````\n\n\n\n== Building\n\n\n\nAs of 1.1.0, JDK8 is required to build
+  the atomic gem, since it attempts to use\n\nthe new atomic Unsafe.getAndSetObject
+  method only in JDK8. The resulting code\n\nshould still work fine as far back as
+  Java 5.\n"
 email:
 - headius@headius.com
 - mental@rydia.net
@@ -56,7 +61,7 @@ files:
 - .gitignore
 - .travis.yml
 - LICENSE
-- README.md
+- README.rdoc
 - Rakefile
 - atomic.gemspec
 - examples/atomic_example.rb