Peter Bex scripsit: > In "bare" symbols I'd expect anything but s-expression delimiters > (spaces, parens, semicolons and possibly single quotes, commas and > backticks) to be allowed but no "special interpretation" of composite > characters. This keeps the reader simple; just consume characters > until you find an s-expression metacharacter.
No Scheme in my list allows " within an identifier. I haven't tested the other special lexical-syntax characters, but I expect all of them except # will be treated similarly. > I think I've argued this point before, but it would be more consistent > to allow \ to escape the | so that || acts exactly analogously to "" > in strings, where backslashes escape the delimiter. > > This is simpler, more regular and allows implementation to use the same > routine for reading strings and symbols (with the delimiter as parameter). Ticket #324 filed. -- If you understand, John Cowan things are just as they are; http://www.ccil.org/~cowan if you do not understand, [email protected] things are just as they are. _______________________________________________ Scheme-reports mailing list [email protected] http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports
