Standalone parser documentation #125
gl-yziquel
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
Hmm I am not sure about exposing those parts. Also, migrating the parsing to something like nom would likely not be possible since it has context dependencies, unfortunately. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Then I'll have to fork it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi.
I'd like to use the
kalk
parsing library to perform various custom stuff, among which some nonlinear and semidefinite programming. As such, I have little use for thekalker
tool, but would appreciate using thekalk
parsing library more thoroughly. Which brings me to three points:As of today, it seems to me that the parsing library is tightly coupled with the evaluation code. Ideally, that should be separate: I want to do my own evaluation and syntactic manipulation.
I do not see documentation for the purely kalk parsing features. I would like to declare some function, and have it parsed, and recovered in my code as an AST. Documentation for that is lacking.
Would it be conceivable to migrate the parsing technology to some parser combinator library like
nom
to allow code reuse ? I'd like to reuse the parsing technology to include some stuff from abstract differential geometry on top ofkalk
.nom
would allow for the kind of code reuse I would need.Is attending to these two issues potentially on the roadmap for kalk ?
Beta Was this translation helpful? Give feedback.
All reactions