Move to an earlier RedCarpet to fix an incompatibility with Rocco. Regen of gh-pages.
Change toBeCloseTo matcher to be more consistent.

It now calculates and compares a difference, rather than rounding
two separate quantities and testing for their equality.
Wrapped the reserved word, "for", in quotes.

This stops it throwing errors in IE and other browsers. I think the newer Firefox and Chrome versions are the only browsers to not die when running it.
Consolidate all waitsFor specs in the same describe block.
Test that afterEach is called after a failing spec.
Test that show that afterEach and after are not being called when a waitsFor times out.
Add 'ensured' blocks to the queue.

This blocks will be run even when a preceeding block sets the abort
flag. This is so that we can support afterEach calls running when the
spec fails due to a timeout.
Regenerate jasmine.js after adding ensured support.
Don't assume exports is defined when window is undefined

The current code makes the assumption that if window is undefined it is
being run in an environment which supports the CommonJS Modules spec.
This is not the case when Jasmine is being run in rhino or SpiderMonkey
(smjs) without EnvJS.

The fix is simply to check that exports is an object.

Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
update jsdoc for jasmine.Matchers.prototype.toThrow
expected argument is optional
create downloads dir if needed during build_standalone_distribution
Fix swapped template values in build_standalone_runner.rb.

`example_source_tags` and `example_spec_tags` each returned what the other
should have returned. I noticed this bug because it made the comments in
SpecRunner.html about where to include spec and source files incongruous with
the example tags that followed.
Add JSDoc @return-tag to 'spyOn' and 'expect' functions support
code completion in Spket IDE
Added toBeNaN matcher
cover spy on on undefined method
less confusing messages for toHaveBeenCalledWith
resolving issue that was identified via pivotal/jasmine#199 where RegExp objects were not properly compared resulting in non-matching RegExp objects to always return true. a patch to jasmine.Env.equals_ adds an extra step for RexExp objects to be compared.
added some specs to strengthen the coverage pivotal/jasmine#234
adding a check for the sticky regExp option supported by Firefox and accepted by the ES6. Note that the tests for this case are checking for the support of the sticky parameter. the logic is still tested by the other expect statements in browsers that do not support sticky but will never enter that block as creating a regExp with that flag is not allowed. Coverage is still good. See pivotal/jasmine#234
When pretty-printing objects, don't include inherited properties.

When making assertions about complex objects, Jasmine's
failure message are sometimes gigantic and difficult
to read because the string representation of an object
contains all of the methods and properties in its
prototype chain. This commit causes the pretty printer
to only display on object's own properties.