>>>>> "mal" == mal <M.-A.> writes:
mal> I have reworded the phase 1 implementation as follows:
mal> 1. Implement the magic comment detection, but only apply
mal> the detected encoding to Unicode literals in the source file.
a. Does this really make sense for UTF-16? It looks to me like a
great way to induce bugs of the form "write a unicode literal
containing 0x0A, then translate it to raw form by stripping the u
prefix."
b. No editor is likely to implement correct display to distinguish
between u"" and just "".
c. This definitely breaks Emacs coding cookie semantics. Emacs
applies the coding cookie to the whole buffer. I don't see a way to
lose offhand, but this is sufficiently subtle that I don't want to
break my head trying to prove that you can't lose, either.
d. You probably have to deprecate ISO 2022 7-bit coding systems, too,
because people will try to get the representation of a string by
inputting a raw string in coded form. This might contain a quote
character.
e. This causes problems for UTF-8 transition, since people will want
to put arbitrary byte strings in a raw string. But these will not be
legal UTF-8 files, even though they have a UTF-8 coding cookie.
People who are trying to do the right thing will have the rules
changed again later, most likely.
This means that until editors reliably implement b. and similar
features, developers must change coding systems to type raw strings
and Unicode strings.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.
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