Kevin Sawicki bc2d0ff0cc Only check ending rules when stack size increases ...

Previously on zero length matches the last two rules were compared
and if they had the same scope name then the last rule was popped
and the remaining line was tokenized using the current scope stack
to prevent infinite parsing loops.

This caused nested method calls in Java to not tokenize correctly
since method rules were sequential in the stack but did not constitute
an infinite loop of zero matches since the stack was currently decreasing.

Now the last two rules are only compared when the stack size is increasing
to prevent this false positive.

Closes #587

2013-06-17 13:08:10 -07:00

..

app

Only check ending rules when stack size increases

2013-06-17 13:08:10 -07:00

fixtures

Remove logging of pid

2013-06-17 12:11:26 -07:00

stdlib

Add spec for Task.once()

2013-06-17 12:11:26 -07:00

atom-reporter.coffee

Fix jasmine styling

2013-04-15 20:45:55 -06:00

jasmine-focused.coffee

Move jasmine-focused to spec folder

2013-03-20 18:36:55 -07:00

jasmine-helper.coffee

Use path.extname() instead of fsUtils.extension()

2013-06-12 15:43:58 -07:00

spec-bootstrap.coffee

Remove hash params from url

2013-06-11 11:17:16 -07:00

spec-helper.coffee

Remove some dead code.

2013-05-29 12:20:56 +08:00

spec-suite.coffee

Rename listTree() to listTreeSync()

2013-06-12 18:26:44 -07:00

time-reporter.coffee

Use node's require instead of internal require

2013-03-12 10:38:05 -07:00