From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: caml-list@inria.fr, "Андрей Бергман" <vkni@yandex.ru>
Subject: Re: [Caml-list] Encodings for ocaml sources
Date: Wed, 22 May 2019 09:01:08 +0200 [thread overview]
Message-ID: <etPan.5ce4f3b4.2f01dc20.291@erratique.ch> (raw)
In-Reply-To: <10553741558487806@myt5-cf6d29327892.qloud-c.yandex.net>
On 22 May 2019 at 03:16:46, Андрей Бергман (vkni@yandex.ru) wrote:
> Latin1, various 8-bit encodings with Latin1 base (character code < 128) and UTF-8,
> all the identifiers should be within Latin1 base,
Latin1 identifiers are deprecated, see [1].
> while string literals can contain any characters?
Yes IIRC they can contain arbitrary *bytes*. But a forward looking habit would be to stick to UTF-8 encoded literals rather use arbitrary bytes and avoid US-ASCII control characters except for white space.
> And UTF-16 is not supported - am I correct?
Yes. Strictly speaking because of the preceeding you can UTF-16 encode the string literals, but for the rest of the program that wouldn't work, the lexer wouldn't recognize the keywords.
> And this is pretty much the same for all Windows/Linux/OSX?
Yes.
Best,
Daniel
[1]: https://caml.inria.fr/pub/docs/manual-ocaml/lex.html#sec77
prev parent reply other threads:[~2019-05-22 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 1:16 Андрей Бергман
2019-05-22 7:01 ` Daniel Bünzli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=etPan.5ce4f3b4.2f01dc20.291@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=vkni@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox