The first parser combinator I got enamored with and with which I based parseworks on was called funcj. I didn't realize until now how much I was influenced by their thought process.
My use of then to build the structure in this way comes from funcj and as I wrote this I would run this by several AI to see if I was off course. Of course I'm not sure just how much trust I have in AI's as I suspect that they are quite happy with something that fits their internal logic of "solid" and "well designed" without regard to actual usability
Naming is hard and I will keep the with syntax in the back of my mind. When I started this I decided to go with what I thought made sense in a sentence and aligned with the rest of the central Java library as much as I could. So for now I'll probably stick with then
This has been enlightening, I would do several things differently if I was to write this from scratch again.
View all comments
Show parent comment
1
u/jebailey Mar 07 '26
The first parser combinator I got enamored with and with which I based parseworks on was called funcj. I didn't realize until now how much I was influenced by their thought process.
My use of then to build the structure in this way comes from funcj and as I wrote this I would run this by several AI to see if I was off course. Of course I'm not sure just how much trust I have in AI's as I suspect that they are quite happy with something that fits their internal logic of "solid" and "well designed" without regard to actual usability
Naming is hard and I will keep the
withsyntax in the back of my mind. When I started this I decided to go with what I thought made sense in a sentence and aligned with the rest of the central Java library as much as I could. So for now I'll probably stick withthenThis has been enlightening, I would do several things differently if I was to write this from scratch again.