…e will include the correct filename and source code information

…script into more-math-operators

Conflicts:
	src/nodes.coffee
	test/operators.coffee

…, ~, !

… of the new operators

Also kill the empty regex :(

…on if they appear at the end of a line

This reverts commit 2e6a781.

… first two characters of the directory into which the compiled files are stored get chopped off.

Example: if compilation invoked like this: 'coffee -o ../lib/ -cw ./', then
Source file: ./OutputFolder/file.coffee, compiled output: ./../lib/tputFolder/
The code only expected '.' to mark the local folder. However, './' is equally valid.

base path for compilation can be './' as well as '.'

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

This try/catch should only be necessary for dynamically loaded files. Also added a lengthier explanation of why this try/catch is needed.

Fixes #2849: use correct filename and code in require()d sources

fix block comment format "\n"

… stack line number patching on by default.

  * Detect initial indentation before the first token and enforce it.
  * Don't add `INDENT` token (or the matching `OUTDENT, TERMINATOR`).

Better handling of initial indent at file start.

…zations-2

Stack trace patch optimizations

  * Avoid excessive search for missing `locationData`
  * Fix `locationData` for `ELSE IF`.

Avoid excessive AST traversal in `updateLocationDataIfMissing`.

check existence of "path" for browser execution

Fix path separator issues in tests.

In #3031, an extensions variable was introduced with file-level scope
that defined the filetypes that CoffeeScript can compile. However, the
Module::load patching calls findExtension() which uses a local variable
called "extensions", which was overriding the outer level one and
causing getSourceMap() to fail.

Avoid variable scope collision with extensions

Updated the Source Maps syntax

Update compiled JS

* Supplement missing block before `ELSE` token only for multi-line `if`.
* Don't prematurely remove `TERMINATOR` before `ELSE` (so we can  differentiate single- and multi-line forms).
* Cleanup: Remove `WHEN` from `EXPRESSION_CLOSE`. (Only `LEADING_WHEN` tokens are preceded by a `TERMINATOR`.)
* Cleanup: Remove really old, inapplicable text from comment.

* When searching for the closing token of a single-line expression, ignore TERMINATORS that will subsequently be removed.
* Add a test.

Instead of throwing the syntax errors with their source file location and needing to then catch them and call a `prettyErrorMessage` function in order to get the formatted error message, now syntax errors know how to pretty-print themselves (their `toString` method gets overridden).

An intermediate `catch` & re-`throw` is needed at the level of `CoffeeScript.compile` and friends. But the benefit of this approach is that now libraries that use the `CoffeeScript` object directly don't need to bother catching the possible compilation errors and calling a special function in order to get the nice error messages; they can just print the error itself (or let it bubble up) and the error will know how to pretty-print itself.

This makes the "stack" property more useful when it's shown on other Node.js applications that compile CoffeeScript (e.g. testing libraries) and should fix #3023. A minimal example:

    $ node -e 'require("coffee-script").compile("class class")'

    /usr/lib/node_modules/coffee-script/lib/coffee-script/coffee-script.js:41
            throw err;
                  ^
    [stdin]:1:7: error: unexpected CLASS
    class class
          ^^^^^

and rename it to `normalizeLines`

Fixed deep directory creation for command line utility

recompile

Instead, set the "stack" property manually when the error gets updated on re-throws.

Fix #3023, Change how error messages are shown

This solves two potential problems when it comes to forking:

    1) Forking will now work correctly even when `coffee` is not installed
       globally.
    2) Forking when using a locally installed version of `coffee` will fork
       using that version, and not fallback to a globally installed version.

Fixes #2957

Fork with binary of coffee-script in use, rather than global

…andom.

Issue #3092: Fix column numbers in sourcemaps to not be essentially random.

…EPL.

This will make packages that modify prototypes - e.g. 'colors', 'sugar'
- work as expected.

To verify that the `node` REPL uses the global context, execute `global
=== module.exports.repl.context`.

Note: Tests pass, except `cluster.coffee`, which, however, failed even
before these modifications.

…istent with the `node` REPL CLI.

(My apologies: In the previous commit I accidentally made `useGlobal:
yes` the default for _programmatic_ use also, but the intent was to
only do it for the stand-alone *CLI*.)

Make the REPL *CLI* use the global context so as to (a) be consistent
with the `node` REPL CLI and, therefore, (b) make packages that modify
native prototypes (such as 'colors' and 'sugar') work as expected.

Note that, by contrast, programmatic use (`require 'repl'`) will
continue to default to a NON-global context - again, consistent with
node's behavior.

…tml)

Use docco to regenerate documentation for underscore.coffee.

Fix broken formatting in underscore.coffee docs

…o using the global context via option `.useGlobal`.

Note that, at least for now, CoffeeScript's own REPL *CLI* still uses a
non-global context, rendering modules such as `color`, which attempt to
modify the prototypes of JavaScript primitives, ineffective. By
contrast, node's own CLI does use the global context.

…h the `node` REPL CLI.

Make the REPL *CLI* use the global context so as to (a) be consistent
with the `node` REPL CLI and, therefore, (b) make packages that modify
native prototypes (such as 'colors' and 'sugar') work as expected.

Note that, by contrast, programmatic use (`require 'repl'`) will
continue to default to a NON-global context - again, consistent with
node's behavior.

…ement0/coffee-script into make-repl-use-global-context

…t-support

Fix: support for consumers of the REPL *module* being able to opt into using the global context ...

…h the `node` REPL CLI.

Make the REPL *CLI* use the global context so as to (a) be consistent
with the `node` REPL CLI and, therefore, (b) make packages that modify
native prototypes (such as 'colors' and 'sugar') work as expected.

Note that, by contrast, programmatic use (`require 'repl'`) will
continue to default to a NON-global context - again, consistent with
node's behavior.

…ement0/coffee-script into make-repl-use-global-context

Some places used 4 spaces instead of 2

Fix some inconsistent indentation

… and jsdoc-like @doctags-comments.

Enhancement: Add more block-comment related tests

Accept all format of numbers in ranges

Fixes #3186

fixed ascii art inconsistencies in coffee's water vapor

…der to be able to auto-require CoffeeScript files.

Fix constructor_destructuring docs example to alert a defined value

… to other (non-fat-arrow-using) long-lived closures.

Format block-comments better

Make the REPL *CLI* use the global context to be consistent with the node REPL *CLI*.

Disallow single-line `IF expr ELSE` without `THEN`

…cit passed-in files.

* Parenthesize compilation of `||=` and `&&=` (when needed).
* Fix variable caching for `?=`

Script loading parallelized in browser

Fix compilation for conditional assignment

Add a new cli option: -g --polling [SPAN]

    If state polling mode is enabled, use it.
    Else use the native api.

    This is useful while watching remote directory.
    Such as the `fs.watch` won't catch the SMB server's file change event.

* Resolves #3059: Don't remove escaped whitespace.
* Fixes #2238: Prevent escaping slashes that are already escaped.
* Fix detection of end of heregex with escaped slashes.

Escaped whitespace and slashes in Heregexes

…y leaves the long option name.

opt: Optimize the comment of the `--watch-polling` option.

Escapable linebreaks in heregexes

* Don't insert unnecessary `_ref` (in the wrong scope)
* Improve code prettiness. (Reverts most of 903e9c9)

Minor fixes for class compilation

* Break up `Closure` and merge `Closure.wrap` into `Base.compileClosure`
* Construct class closure directly in `Class.compileNode`
* Reuse `isLiteralArguments` in `Range.compileArray`
* Move all helpers to bottom of file
* Add test for #3063

* Make scope of `Code` nodes accessible (prior to `compileNode`)
* Use correct scope for reference of external constructor.
* Remove unreachable code.

Fix scope of external constructor reference / Refactor `Closure`

Avoid unnecessary wrapping of some bound functions

Clean up `Method calls on splice endpoints`

 * Make `compilePath` synchronous
 * Remove unused variable

Fixes #3087 -- Use `fs.*Sync` for CLI compilation

  * Fixes #2949: Detect reserved names (not only for instance methods)
  * Don't assign names which might result in incorrect `super` calls

(and remove duplicate `context` assigment)

Fix super-related tagging of `Code` nodes

add: Stat polling support while `fs.watch` doesn't work.

This reverts commit 52789f5.

… and only leaves the long option name."

This reverts commit 08f6c65.

This reverts commit 2853e71.

Implements #3229 - Changed multiline string literals

Fix multiple escaped backslashes in literal strings

  * Use absolute paths for source files and target paths
  * Memorize and explicitly check for watched directories
  * Make path comparison and construction more precise and clear
  * Remove now unnecessary check for special relative paths

  * Move all source path filtering to `compilePath`
  * Restrict modification of `sources` to
    * `compilePath` for adding
    * `removeSource` for removing
  * Don't add unfiltered paths to `sources` (and remove them later on)

CLI fixes and refactoring

 Implements #3249, #1994 Escape newlines in heredocs with backslashes

Don't register nested variables of complex parameters as parameters of the compiled function. Use the computed placeholder name instead.

Fix #1766, Add negative slice end index into docs

Implement #1495,  Method call chaining

Fix #1273, Handle backslashes at the end of heredocs

  * Exclude trailing blank line from the match group
  * Fix backslash handling

  * Suppress `EPERM` from watchers
  * Suppress `EPERM` from `fs.unlink`

Fixup #3263: Prevent loop collection in endAllImplicitCalls

Add CoffeeScript in Action book link

Fix --watch handling of deleted sources

You can now `require('coffee-script/register')` to manually register,
and the compiler auto-registers when directly running a coffee file.

…egistration

fix require.extensions registration

…ing, idioms: calls, comprehensions, interpolations

Examples: Back to non-naked constructor, @, preincrement, comprehension bracketing...

the page lists only top 100 contributors

Format utilities using single quoted literals

  * Preserve `options` when called without `args`
  * Don't use `coffee` script as `execPath` (Fixes #2919)

Fix multiple postfix conditionals

Fix `child_process.fork` patch

`coffee DIR` executes `DIR/index.coffee`

ref michaelficarra/CoffeeScriptRedux#266 and michaelficarra/CoffeeScriptRedux@670a1f5#diff-2

Chaining semantics after arguments with outdent

Fix 1096, 1131, 1828: Improve error messages for generated tokens

Fix #1275

Fix #1099, remove in empty array optimization

Fixes #1871, close implicit objects in implicit returns

Implement #156, Added expansion to destructuring

Fix expansion in destructuring inside comprehensions

Conflicts:
	lib/coffee-script/grammar.js
	lib/coffee-script/lexer.js
	lib/coffee-script/nodes.js
	lib/coffee-script/parser.js
	test/regexps.coffee

Add new mathematical operators

Fixes #3216 for declarations in object literals

Fixes #3325: implicit indendation error messages

Fixes chaining after inline implicit objects

Prepare 1.7.0 release

Implement #3332