freenode/#clasp - IRC Chatlog
Search
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
14:48:02
scymtym_
beach: what should we do for the undefined consequences in 2.4.8.7? all implementations i tested do (read-from-string "#b12.") => 12 5 but (read-from-string "#b12") |- error
15:07:24
scymtym_
ACTION is getting very close to having all reader macro functions fixed and fully covered by tests
15:13:33
beach
scymtym_: I am willing to be stricter than those implementation and signal an error in both cases.
15:15:07
scymtym_
yeah, the first one seems strange to me. but since all implementations seem to do it, i thought i might be missing something
16:51:43
drmeister
scymtym_: Sorry - running errands. My plan is to get it running and building the objects in chemInfo.h in the next couple of weeks.