caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Dave Berry <dave@kal.com>
Cc: John Max Skaller <skaller@ozemail.com.au>,
	Markus Mottl <mottl@miss.wu-wien.ac.at>,
	OCAML <caml-list@inria.fr>
Subject: Re: Unicode (was RE: JIT-compilation for OCaml?)
Date: Thu, 11 Jan 2001 19:49:16 +0100	[thread overview]
Message-ID: <20010111194916.B4332@pauillac.inria.fr> (raw)
In-Reply-To: <3145774E67D8D111BE6E00C0DF418B663AD720@nt.kal.com>; from dave@kal.com on Thu, Jan 11, 2001 at 12:58:53PM -0000

> I thought Unicode was a recognised subset of ISO-10646, corresponding to the
> range 0-2^16.  Also, don't Windows NT/2000 use Unicode?  

Yes, Win32 (i.e. 95, 98, ME, NT, 2000 and whatnot) uses 16-bit
characters.  Java too.  But Unix C libraries that support wide chars
seem to prefer 32-bit characters.  Remember:

    "Standards are great: there are so many to choose from."

> (I realise this isn't directly on-topic, but it may be relevant for future
> extensions to OCaml?)

It is very relevant indeed.  We've been contemplating adding some
simple support for wide characters and wide strings, e.g. as two new
library modules, but the stumbling point is whether to use 16-bit or
32-bit wide characters.  While 32 bits is probably the wave of the
future, 16 bits is what we need to interface easily with Java and with
many Microsoft products (e.g. COM dispatch components, Visual Basic,
various Win32 APIs).

Shall we "do it right" (for some notion of "right") or favor
interoperability?  Hard question.  My current answer is to
procrastinate...  Actually, multi-byte encoded strings (UTF-8) are not
so bad and already have full support in OCaml :-)

- Xavier Leroy



  reply	other threads:[~2001-01-12  9:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 12:58 Dave Berry
2001-01-11 18:49 ` Xavier Leroy [this message]
2001-01-12  9:24   ` John Max Skaller
2001-01-12 12:05   ` Pierpaolo BERNARDI
     [not found]   ` <3A5F7685.FF2593BB@snob.spb.ru>
2001-01-12 21:33     ` Nickolay Semyonov
2001-01-17 19:47       ` John Max Skaller
2001-01-12  0:19 ` Pierpaolo BERNARDI
2001-01-17 19:37   ` John Max Skaller
2001-01-18 17:49     ` Pierpaolo BERNARDI
2001-01-22 20:27       ` John Max Skaller
2001-01-22 21:44         ` Pierpaolo BERNARDI
2001-01-24 13:41           ` John Max Skaller
2001-01-12  8:33 ` John Max Skaller
     [not found]   ` <3A5F77B7.52D8F933@snob.spb.ru>
2001-01-12 21:33     ` Nickolay Semyonov
2001-01-12 21:25 ` Nickolay Semyonov
     [not found] <Pine.GSO.4.00.10101222155260.697-100000@carlotta.cli.di.unipi .it>
2001-01-22 21:57 ` Pierpaolo BERNARDI

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=20010111194916.B4332@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=dave@kal.com \
    --cc=mottl@miss.wu-wien.ac.at \
    --cc=skaller@ozemail.com.au \
    /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;
as well as URLs for NNTP newsgroup(s).