-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Req: Performance comparison will be good #83
Comments
Any insight into algorithm specifics? |
may be this? |
Ok, that's very interesting. It uses diffs instead of specific origins to
determine if it can reuse an earley set. Also looks like it is caching at
the set level rather than the item level. It can do that because of the
diffs.
…On Sun, Aug 27, 2017, 12:39 PM ArsenShnurkov ***@***.***> wrote:
may be this
<https://raw.githubusercontent.com/vnmakarov/yaep/master/Internals.txt>?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#83 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AALIfus5S52ELDcxG-UHElFVwPogN0vEks5scZuygaJpZM4PDV5z>
.
|
After further digging, looks like a derivative of the DEEP (Directly Executable Earley Parser) with the addition of Frame grouping and origin differentials. I'll have to look into this further. To speak to the original opened issue: To get benchmarks, I'd have to pull in an ANSI C Grammar. I have one defined in bnf in the benchmarks project, but haven't used it to parse anything. I was mostly using it to test the bnf parsing. |
speedup for special case |
this implementation claimed to be fastest:
https://github.com/vnmakarov/yaep
it's readme file contain performance comparison with Marpa and yacc
The text was updated successfully, but these errors were encountered: