You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I comment out the for loop it parses an invalid expression in 73ms.
When I uncomment the loop it needs about 3s to parse the expression.
As far as I see, the loop is connected to gathering expected tokens in case of error. Can it be preprocessed upon the creation? Can some internal loops be omitted? What is the LHF you mentioned?
The text was updated successfully, but these errors were encountered:
It is time to do an update to new versions of node again. Also, the first pass debugging never quite worked correctly in catching syntax errors, and I never got back around to fixing the issue. I will assign myself this issue and work on a version bump for node 10+ support as well as first pass improvements.
LHF meant Low Hanging Fruit, things that were simple optimizations that anyone interested in the repo could contribute to, or myself given time.
Hello.
First of all, thanks for (as I believe) the only working BNF powered script parser for NodeJS.
On the other hand it has some flaws obstructing the usage.
In particular I saw the problem:
nodebnf/BnfRules.js
Line 288 in d2739ec
When I comment out the for loop it parses an invalid expression in 73ms.
When I uncomment the loop it needs about 3s to parse the expression.
As far as I see, the loop is connected to gathering expected tokens in case of error. Can it be preprocessed upon the creation? Can some internal loops be omitted? What is the LHF you mentioned?
The text was updated successfully, but these errors were encountered: