delta/node.git/test/simple/test-repl.js, branch move-debugger-tests

repl: Catch syntax errors better

2013-09-04T18:13:41+00:00

Replace the growing list of 'isSyntaxError' whackamole conditions with a
smarter approach.  This creates a vm Script object *first*, which will
parse the code and raise a SyntaxError right away.

We still do need the test function, but only because strict mode syntax
errors are not recoverable, and should be raised right away.  Really, we
should probably *only* continue on "unexpected end of input" SyntaxErrors.

Also fixes a very difficult-to-test nit where the '...' indentation is
not properly cleared when you ^C out of a syntax error.

Closes #6093

test: fix up indentation, replace tabs with spaces

2013-07-10T07:48:57+00:00

repl: fix JSON.parse error check

2013-05-30T12:41:00+00:00

Before this, entering something like:

> JSON.parse('066');

resulted in the "..." prompt instead of displaying the expected
"SyntaxError: Unexpected number"

repl: isSyntaxError() catches "strict mode" errors

2013-03-30T20:10:30+00:00

Closes #5178.

repl: make built-in modules available by default

2013-01-12T20:10:29+00:00

Closes #3564.
Closes #4578.

REPL: fix floating point number parsing

2013-01-04T01:11:54+00:00

In JS, the expression ".1" is a floating point number.  Issue 4268 concerns the
REPL interpreting floating point numbers that lead with a "." as keywords.  The
original bugfix worked for this specific case but not for the general case:

    var x = [
        .1,
        .2,
        .3
    ];

The attached change and test (`.1+.1` should be `.2`) fix the bug.

Closes #4513.

repl: don't interpret floating point numbers

2012-11-10T17:21:17+00:00

Don't interpret floating point numbers, e.g. ".1234", as REPL commands.

Fixes #4268.

repl: ensure each REPL instance gets its own "context"

2012-10-12T23:37:17+00:00

Before there was this weird module-scoped "context" variable which seemingly
shared the "context" of subsequent REPL instances, unless ".clear" was invoked
inside the REPL. To be proper, we need to ensure that each REPL gets its own
"context" object. I literally don't know why this "sharing" behavior was in place
before, but it was just plain wrong.

repl: make "end of input" JSON.parse() errors throw in the REPL

2012-10-01T18:36:06+00:00

repl: make invalid RegExp modifiers throw in the REPL

2012-10-01T05:47:57+00:00

Fixes #4012.