lightparse: improve the detection of regexp about js.metaret HOT 4 CLOSED

Looks complicate to implement with the current implementation.
Maybe a fix would be to start with a separate tokenizer, e.g. pick the one from narcissus:
http://glat.info/jscheck/narcissus.jsparse.js

Also using narcissus function declarations and named function expressions could be properly distinguished (not sure it would matter here, though), and - more important - automatic semi-colon "insertion" would be supported.

Mmmm humbling lesson. Maybe I'll just switch the lightparse.js internal implementation to narcissus, while still offering the same interface to the outside.

from js.metaret.

Note: Using narcissus would require to make it extendable so that it recognizes metaret, metafun and inline.

from js.metaret.

Found several other issues which become difficult to solve using lightparse. Again narcissus would be desirable here (or any equivalent). In particular, lightparse callArr does not distinguish between function declarations / expressions / actual calls.

Another complication: add support for dotted function declaration names (for metaparse etc.).

Maybe for the time being we can just stop trying to shorten local names using lightparse, and do it separately afterwards.

from js.metaret.

acorn looks like a good candidate for a parser : small yet complete implementation.

from js.metaret.