This is a somewhat old issue, but I wonder how '|' symbol-escapes ended up excluding '|' and '\' inside it. Does it intend a room for future extension that vertical bar and backslashes can be included in '|' symbol escapes by escaping them with '\', as in CL? I searched tickets in the WG1 trac site but couldn't find the discussions on it except ticket #16.
It's not that I'm opposing to the current syntax. To include vertical bar or backslash, I can still use \x7c; and \x5c; without '|'-escapes. I'm just curious about the rationale of the decision out of various options, notably: - Excluding '|' within |-escapes are understandable, but why '\' is excluded, especially if we don't allow to any extra escaping insinde '|'s? - CL also has '|'-escapes but they don't delimit symbols, so |abc|def|ghi| is read as a single symbol abcDEFghi. R7RS doesn't explicitly say '|' delimits the symbol, but also doesn't seem to allow |abc|def syntax according to 7.1.1. I'm fine with either way, but was it a conscious decision? _______________________________________________ Scheme-reports mailing list [email protected] http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports
