Strange behavior when parsing CallExpression arguments

Hello! Thanks for such a great work!

Found a strange behavior when parsing CallExpression arguments. Don’t know if it is intended but let’s find out together.

So here is an example:

foo(asdf, sdf, asd, sdf) // valid expression
foo(asdf sdf asd sdf) // valid expression, same output as above

// here comes the weird part
foo(asdf, sdf asd sdf) // valid, 4 args
foo(asdf, sdf, asd sdf) // valid, 4 args
foo(asdf sdf, asd, sdf) // Unexpected token , at character 13
foo(asdf sdf asd, sdf) // Unexpected token , at character 17

I expect two last examples to be either both 4 args, or 3 and 2 args respectively. But it gives an error.

[6utt3rfly]

Thank you for reporting, @Kot-Zakhar !

It looks like the code was adding expressions to the argument, even if there wasn’t a comma separator. However, it also has a check for a missing argument (foo(,) , foo(,1,2), foo(1,,2) and foo(1,2,)) that was inadvertently catching some of your cases after it found a comma. I’ve created a fix for this that can hopefully make it into the next release.

[grimalschi]

@6utt3rfly sounds very good. By the way I want to thank you and other contributors for developing and maintaining this library. I have forked it to build my own parser (heavily based on jsep) for parsing formula expression in my project.