Re: [Scheme-reports] inconsistent use of \| escape
John Cowan 30 Sep 2013 04:35 UTC
Vassil Nikolov scripsit:
> For example (it is a rare case, but I have encountered it), when
> generating literal strings programmatically and not having a way
> to determine what character is inserted in the generated value,
> it is convenient to simply precede the unknown character with the
> escape character and rest assured that the string literal will always
> be well-formed.
We actually don't do that, and for this reason: If it was guaranteed that
\q meant the same as q, it would be impossible to give \q a meaning in
some future version of the language. Therefore, we say that \q is
undefined, so that it can be treated by an implementation as an error,
as q, or as something new in advance of future standardization.
--
John Cowan cowan@ccil.org http://www.ccil.org/~cowan
C'est la` pourtant que se livre le sens du dire, de ce que, s'y conjuguant
le nyania qui bruit des sexes en compagnie, il supplee a ce qu'entre eux,
de rapport nyait pas. --Jacques Lacan, "L'Etourdit"
_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports