Noah Lavine <noah.b.lav...@gmail.com> writes: > Hi all, > > When I was looking at this a while ago, it looked like a big issue > (possibly *the* big issue) with Guile's parser is that it doesn't do > automatic semicolon insertion. (In Javascript, semicolons are optional > in certain contexts, when the place where the semicolon would be is > followed by a newline.)
And the ambiguities around the / operator. Dealing with the / operator the tokenizer has to decide whether it's a divide operator or a RegExp literal, which needs the context from the parser. This explains the 39 Math.NL errors that I forgot in previous mail. Kanru
