Re: Forth 200x, S\\\q
- From: anton@xxxxxxxxxxxxxxxxxxxxxxxxxx (Anton Ertl)
- Date: Tue, 19 Feb 2008 16:44:07 GMT
Bruce McFarling <agila61@xxxxxxxxxxxx> writes:
So rather than saying that the \xHH representation assumes 1 char = 1
byte = 1 au, it is more precise to say that it assumes that:
1 char >= 1 byte
and that where characters are larger than 1 byte, each character may
be unambiguously encoded as a sequence of bytes. Which, for Unicode,
is the case.
There are a number of options what \xHH means in a Unicode Forth:
- It means the Unicode code point HH, encoded according to the
system's encoding; e.g., with UTF-8 some \xHH characters would be
translated into two bytes.
- It means a (primitive) char (i.e., byte) with the value HH. What it
means as Unicode character depends on the system's encoding and
possibly on the surrounding chars; you could construct a sequence of
chars with \x that would be illegal as UTF-8 encoded Unicode
characters. I think Stephen favours this option, because it allows
specifying, say, I/O control strings that should not be interpreted as
UTF-8 strings.
- anton
--
M. Anton Ertl http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
New standard: http://www.forth200x.org/forth200x.html
EuroForth 2008: http://www.complang.tuwien.ac.at/anton/euroforth/ef08.html
.
- References:
- Forth 200x, S\\\q
- From: Marcel Hendrix
- Re: Forth 200x, S\\\q
- From: Stephen Pelc
- Re: Forth 200x, S\\\q
- From: Stephen Pelc
- Re: Forth 200x, S\\\q
- From: Bruce McFarling
- Forth 200x, S\\\q
- Prev by Date: Re: FORTH levels
- Next by Date: Re: Particle Swarm Optimization
- Previous by thread: Re: Forth 200x, S\\\q
- Next by thread: Re: Forth 200x, S\\\q
- Index(es):
Relevant Pages
|
Loading