Add opal to guard implementations
Merge pull request #40 from elia/patch-1

Add opal to guard implementations
Fix ensure to unregister version guard.
Fix a helper IOStub when calling IOStub#puts without arguments

This commit keeps calling self.write.
Not directly self << "\n".
Use Range#{begin,end} instead of Range#{first,last}

* Avoid Range#last to follow [Bug#8739](http://bugs.ruby-lang.org/issues/8739)
* Avoid Range#first to adjust style with Range#last
Corrected rspec 2.14 deprecation warnings.

RSpec 2.14 deprecated a lot of things, in preparation for rspec 3. When I run the test suite with rspec 2.14 I get a huge number of deprecation warnings (more than one per file), which makes the results very difficult to read. I've corrected the specs where they were using outdated methods. The highlights were:

* stub!() => stub()
* mock() => double()
* should_receive().any_number_of_times => should_receive().at_least(:once) or stub
Merge pull request #46 from iainbeeston/rspec_deprecation_warnings

Corrected rspec 2.14 deprecation warnings.
Revert "Merge pull request #46 from iainbeeston/rspec_deprecation_warnings"

Since I made this PR I've come to think this was a bad idea. MSpec defines it's own methods that have the same name as built in rspec methods, such as stub!() and mock(). Before the commit below, some of the tests were raising rspec deprecation warnings *while calling MSpec-specific methods*. They shouldn't have been raising deprecation warnings at all if they were correctly calling the MSpec methods. This makes me think that RSpec was overwriting the MSpec methods on Mock and Object, and the MSpec methods were not being called at all, but because the functionality is almost identical, it wasn't obvious that this was happening until they started showing deprecation warnings.

For a good example of this, see mock_spec.rb. Under RSpec < 2.14.2 this runs fine. But on 2.14.2 it shows a number of deprecation warnings, while calling what should have been MSpec-specific methods.

I'd put more thought into fixing this problem, but if RSpec is going to be replaced in MSpec 2 it doesn't seem worth the effort to make such a painstaking change to the test suite.
Merge pull request #47 from iainbeeston/rspec_deprecation_warnings

Revert pull request to fix RSpec deprecation warnings
Removed language_version from mspec.
Exposed ProfileFormatter for mspec help.
Removed implementation dependent example for equal matcher.

MRI 2.0 treats Floats as immediates if double-tagging is used.
Removed Gemfile.lock for mspec.

In RSpec, raise_error and raise_exception are aliases. Since "error"
is a more general term, it's reasonable that it matches "kinds of"
exceptions. Here, raise_exception is used to match only a specific
kind of exception. Any confusion that results will be short-lived
as MSpec 2.0 will use a different syntax.
Added raise_exception to MSpec.
Renamed deprecated calls to File.exists? to File.exist?

* It prints a warning in recent ruby (2.1)
Merge pull request #49 from eregon/file_exist

Renamed deprecated calls to File.exists? to File.exist?
Merge pull request #41 from chrisseaton/unregister-fixes

Fix ensure to unregister version guard.
Merge pull request #44 from kachick/avoid-range-last

version-guard should use Range#{begin,end} instead of Range#{first,last}
Merge pull request #43 from kachick/fix-helper-io_stub-puts

IOStub#puts should append "\n" when argument not given
Bumped version to 1.5.21.