-
Notifications
You must be signed in to change notification settings - Fork 20
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
abandoned or live? #37
Comments
Abandoned. There was however a workshop on parsering just last week at JuliaCon. |
Thanks @oxinabox. I did watch that video and had a look at his project but couldn't work out how to actually use it. I was able to get a parser up in a couple of hours with this project, before hitting performance and debugging problems. I think it's due to backtracking but without better debug tooling I can't really work out what to do to fix things. My dream is of a parsing environment where i can fire up a notebook session and start writing a parser against a library of inputs and get real-time parse graphs plotted for me and highlighed parsed text to figure out what's going on. |
FYI, in the absence of @andrewcooke we finally managed to release the new version (2.1.0), which should work with the recent Julia and packages. |
@alyst thanks - did you release it here or on a forked github project? Julia has the potential to enable really efficient combinator parsers, as the method overloading would let us rewrite easy to understand but inefficient combinations of primitives in to efficient but difficult to understand ones. But like you, I don't have the hours to maintain it. |
@drdozer No, it's not forked, it's the very same package. It's possible for package "collaborators" to trigger the release via juliahub.org. |
|
Hi - I was wondering if this project is alive or has been abandoned? I wanted to try to use a combinator-based parser in julia and found this one. However, there haven't been any git commits for a while. I've hit a snag where StarPlus tends to get stuck in stupidly deep recursions, and have also found the error reporting to be a bit difficult to follow but don't really want to end up as the only user/developer of a library.
The text was updated successfully, but these errors were encountered: