correct terminology for referring to strings - Erlang Programming

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion correct terminology for referring to strings
Received-SPF: pass (google.com: domain of erlang-questions-boun...@erlang.org designates 192.121.151.104 as permitted sender) client-ip=192.121.151.104;
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
 h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
 b=EiYBuYrOcnCFLgTyRB1mWv3ZbOxTfRdnDH6cvEq2GQu376wGkMvb5EplsMqsutj2Qj2/4ftdxFkPYDTCJYj6SQ6MdksafEX60uQBhqgoOqmbpiRKjy4jPEFZzlmMIOA5kz0HIJa4iMJOxtItjrxM+VbSKxEr+S6ZEJIPdsnJoxw=;
References: <CAANBt-roo9uFTsrZw2nFq0=_7Z=W-hFXYLNLnP1Phm_5+i2...@mail.gmail.com>
 <5017C60F.1050...@gmail.com> <5017E5D5.2030...@gmail.com>
 <CAKrexV+F3J_ngBdgcD9T-7==gHmFb66ZwvSfjoqXwGbYNd=...@mail.gmail.com>
 <5018EB2B.5030...@gmail.com>
 <1343846574.80867.YahooMail...@web111403.mail.gq1.yahoo.com>
 <C0436E74-D50E-4D9B-A0CC-160ADA241...@cs.otago.ac.nz>
Message-ID: <1343909141.62398.YahooMail...@web111404.mail.gq1.yahoo.com>
Date: Thu, 2 Aug 2012 05:05:41 -0700 (PDT)
From: Thomas Lindgren <thomasl_erl...@yahoo.com>
To: "erlang-questi...@erlang.org" <erlang-questi...@erlang.org>
MIME-Version: 1.0
Subject: Re: [erlang-questions] correct terminology for referring to strings
Precedence: list
Reply-To: Thomas Lindgren <thomasl_erl...@yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Errors-To: erlang-questions-boun...@erlang.org
Sender: erlang-questions-boun...@erlang.org



It might well be a wooly-headed idea when you look at the details, and I co=
nfess to not being an expert in this area. The basic concept would be to wa=
rn when, for instance, you've entered your string literals in Latin-1 when =
the compiler or system options decree that you should use UTF8. I like the =
overall idea of not leaving encoding problems to the good will of external =
tools, but if it can't be detected reliably, then it's of course just dream=
ing.=A0

Another approach might be to use a heuristic tool a la xref to detect "susp=
icious" string literals. Not sure if that helps.

Best,
Thomas


----- Original Message -----
> From: Richard O'Keefe <o...@cs.otago.ac.nz>
> To: Thomas Lindgren <thomasl_erl...@yahoo.com>
> Cc: "erlang-questi...@erlang.org" <erlang-questi...@erlang.org>
> Sent: Thursday, August 2, 2012 3:28 AM
> Subject: Re: [erlang-questions] correct terminology for referring to stri=
ngs
> =

> =

> On 2/08/2012, at 6:42 AM, Thomas Lindgren wrote:
>> =

>>=A0 How about adding compiler warnings about string literals that do not =
obey
>>=A0 the designated encoding? (There should then, of course, be multiple =

> possibilities to choose from.)
>> =

> =

> What does this actually mean?
> =

> There is no byte sequence valid in UTF-8 that is not also
> valid in Latin-1.=A0 Yes, codes 128..159 are control characters,
> but nobody ever said that control characters weren't legal in
> strings.=A0 Checking the mappings that came with Unicode 4,
> there is no byte sequence valid in UTF-8 that is not also
> valid in ISO 8859-{1,2,4,5,9,10,13,14,15}, PC code pages
> 437, 737, 775, 850, 852, 885, 86[012356], and Apple Arabic,
> Central European, Croatian, Cyrillic, Farsi, Greek, Hebrew,
> Icelandic, Roman, Romanian, Squeak, and Turkish.
> =

> So I have no idea what "string literals that do not obey
> the designated encoding" means or how to operationalise it.
>

_______________________________________________
erlang-questions mailing list
erlang-questi...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
