12:17:02beachFor 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:57scymtym_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:27beachThey would have to intercept calls to READ-COMMON I suppose.
12:18:31scymtym_unless it defines a method on READ-COMMON the way the eclector-concrete-syntax-tree does
14:48:02scymtym_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:24scymtym_ACTION is getting very close to having all reader macro functions fixed and fully covered by tests
15:13:33beachscymtym_: I am willing to be stricter than those implementation and signal an error in both cases.