Minor embellishments

Move execution of the compiled code inside the try/catch block:

    try
      js = CoffeeScript.compile "_=(#{input}\n)", {filename, bare: yes}
    catch err
      cb err
>   cb null, vm.runInContext(js, context, filename)

    try
      js = CoffeeScript.compile "_=(#{input}\n)", {filename, bare: yes}
>     cb null, vm.runInContext(js, context, filename)
    catch err
      cb err

Since the move to the nodeREPL package, input lines to be evaluated are
now wrapped in parentheses; that is:

    'foo'

would become:

    ('foo'
    )

The old way of detecting empty lines was to see if the input string was
either totally empty, or whitespace-only. The addition of these
parentheses breaks that.

In order to fix this, we simply tweak the regex a little to ignore these
added parentheses if they're present. As an added bonus, the regex
should match empty inputs even if they aren't.

This also makes the "empty command evaluates to undefined" test pass,
for the right reasons (i.e. not because of the broken error behavior
from before).

Fix REPL crashing on execution error

by handling them together.

Implicit object/implicit call interaction handling

Hoist build function to top level of Cakefile

Move filename processing to a `parseFileName` function in
helpers.coffee.

Map `.coffee.md` as a Literate CoffeeScript extension.

Also, make .litcoffee and .coffee.md files executable without their file
extension - eg. `coffee test` would work for a file called
`test.litcoffee`.

Add support for text/literate-coffeescript in the browser

…onal, which is a deeply regrettable accident of history that I would not repeat, given the chance.)

Fix implicit calls with try/catch/finally as arguments

…uctors

Revert #2599

f
  a

and only allow cases like:

f
  a: 1

…first-argument-only-on-implicit-object

Disallow implicit calls in cases like:

…keep .litcoffee as the canonical, however.

These are the modifications I had to do in order to get source maps working
in 27.0.1425.2 (Official Build 185250) canary. I haven't tested other
browsers.

I first looked at the V3 spec and a few examples, and I saw that the
`source` key of the source map should be called `sources`.

After doing the `source` to `sources` change, the coffee source and for
some odd reason the javascript file would not show up in the browser
dev tools (it was being fetched but not evaluated).

To fix this, I had to add the coffee source to the `sources` list in the
source map file.

Conflicts:
	lib/coffee-script/coffee-script.js
	lib/coffee-script/nodes.js
	src/nodes.coffee

…into sourcemaps

…he .map file.

…ping().

…rray, and return the SourceMap object.

…s in commnets.

* Offset @chunkLine for inserted line break.
* Avoid line break insertion for blank lines.

Fix line number mismatch when first line is indented.

…t actually has a chance in hell of calling the correct thing.

… instance properties in a class body.

…ared.

Conflicts:
	lib/coffee-script/coffee-script.js
	lib/coffee-script/command.js
	lib/coffee-script/nodes.js
	src/coffee-script.coffee
	src/command.coffee
	src/nodes.coffee

Small typo fix (:

Fix Source Map Generation for 1.6.0