This page is part of the web mail archives of SRFI 75 from before July 7th, 2015. The new archives for SRFI 75 contain all messages, not just those from before July 7th, 2015.
I agree that certain characters ought not appear in identifiers without use of some escape mechanism. But rather than list them, I'd prefer to do it by category. Just looking at the categories, I think characters with the "General Category" of CC (control characters) CF (formatting controls), PS (open punctuation), PC (close punctuation) ZL (line separator), ZP (paragraph separator) and ZS (space separator) should probably be excluded from identifiers. PS includes our familiar open-paren, open-bracket, open-curly, and many other symbols, most of which were in your list. PC includes the closing versions of each. ZL, ZS, and ZP, as I understand it, basically means whitespace of various kinds. And CC and CF characters, where they are not whitespace, are still probably not good ideas for identifiers. If we want to reserve a bunch of characters for reader macros in implementations where reader macros are definable, I'd suggest the class SO (other symbols, including dingbats); they're eyecatching, occasionally iconic, and for the most part linguistically neutral. Bear