libera/#sicl - IRC Chatlog
Search
12:40:41
beach
scymtym: Do I understand things right that the architecture builder protocol is quite stable, although it needs more documentation, whereas the way the packrat parser uses the architecture builder protocol is still experimental? And what about the packarat parser itself?
12:45:07
beach
I think I am starting to see what parts of the code for the architecture builder protocol I need to look at more carefully, and what parts I can safely ignore.
12:46:40
scymtym
beach: architecture.builder-protocol is pretty stable. parser.packrat uses architecture.builder-protocol mostly as an implementation detail. but /clients/ of parser.packrat may use a.b-p to construct their parse results. parser.packrat might still change a lot internally but the provided interface should not change too much
12:56:07
beach
I see. But wasn't the use of keywords vs something else an issue that might impact how clients use the packarat parser?
12:58:32
beach
How clients use the combination of the packrat parser and the architecture builder protocol I mean.
13:20:32
beach
So, as I understand things, the "parser"-side client of the architecture builder protocol determines the meaning of these parameters. In this case, it's the packrat parser that makes these choices, and some others, like what node kinds there are.
13:21:36
beach
Any "consumer"-side client must therefore be able to rely on these things being stable.
13:24:14
beach
Also, it would be good if these parameters and node kinds were independent of the parsing technology being used.
13:26:02
beach
And if so, perhaps we should specify these node types and kind parameters for each special form and each standard macro.
14:49:17
scymtym
i'm mostly away from the computer today. so i won't answer immediately anyway. one important difference is that parser.packrat is a parser generator, that's why mentioned its use of the builder protocol not mattering. something like the s-expression syntax library would be on the "parser"-side and thus define the used kinds and relations. and those kinds and relations should indeed be independent of the used parsing technology
14:50:48
beach
Oh, yes, sorry. I meant to say the s-expression-syntax library, not the packrat parser library.