freenode/#clasp - IRC Chatlog
Search
7:57:46
beach
scymtym: In the Eclector documentation, for NOTE-SKIPPED-INPUT, I would like to be able to say something about the position of the stream when this function is called. Is it correct to say that when it is called, the stream is positioned immediately after the skipped input?
7:59:03
beach
scymtym: What I am working on is to replace the hacked reader in Second Climacs with Eclector. My plan was to kill two birds with one stone and see whether I could use only the documentation to understand what needs to be done.
8:18:07
beach
scymtym: OK, I wrote something in the documentation. You may want to check that I didn't lie.
10:47:10
scymtym
beach: while we still have to get the documentation for ECLECTOR.READER:NOTE-SKIPPED-INPUT right, note that there is higher-level protocol ECLECTOR.CONCRETE-SYNTAX-TREE:RECORD-SKIPPED-INPUT which constructs the source range for the client
12:17:02
beach
For Second Climacs I am not using CSTs though. I use a lower-level concept that preserves the read order rather than the order of the children in an expression.
12:17:57
scymtym_
beach: i think your description is accurate except for the fact that a client may not generally be able to keep track of the start position in case of recursive read calls
12:18:31
scymtym_
unless it defines a method on READ-COMMON the way the eclector-concrete-syntax-tree does
12:19:09
scymtym_
exactly. that method binds a special variable to stash the start position for retrieval in NOTE-SKIPPED-INPUT
12:20:04
scymtym_
that could warrant a small separate section since it describes the interaction of multiple protocols