tim wrote: > > to be fully backwards compatible, this means that the compiler > > should use 8 bits, no matter what string type you're using. ... > I think the real problem here was MAL's generalization of \x to 2-byte = stuff > in Unicode strings. If Unicode strings *have* to support \x, then >=20 > \x0123456789abcdef >=20 > in Unicode strings should act like >=20 > \u00ef >=20 > in Unicode strings, and SRE should play along with that too. \x was = broken > to begin with; better to wipe it out than try to generalize it. I think this means that we agree -- \x is a wart that can only be used to embed *binary bytes* in a string. </F>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4