[M3devel] UTF-8 TEXT

[Daniel Alejandro Benavides D.]

Hi all:
it can't be used like that (as in DEC-SRC early versions) because TEXT is opaque type, you can't reveal it like that at that level.
Anyway whoever needs characteristics of JVM or so languages must know that the likes are very inefficient, and C is pretty nit but also very much UNSAFE, perhaps if somebody wants that maybe should use integer strings  to map directly from hardware every symbol of the computer (but support every kind of format seems over-complex in space and time) Operating system normally doesn't handle I/O in many cases, but the I/O subsystem (like Windows I/O) and in some cases it takes advantages of not waiting for a thread to return control over the app.
There are many computers that use non-ASCII terms but normally they support that script, so why put more weight on it? Maybe I should ask either lexicographers or specific language users to know what they need for they in a comprehensible manner and not hard coded standards many don't use still.
Thanks in advances

--- El jue, 28/6/12, Dragiša Durić <dragisha at m3w.org> escribió:

De: Dragiša Durić <dragisha at m3w.org>
Asunto: Re: [M3devel] UTF-8 TEXT
Para: "Hendrik Boom" <hendrik at topoi.pooq.com>
CC: m3devel at elegosoft.com
Fecha: jueves, 28 de junio, 2012 07:48

glyph sounds better, I agree! :)

On Jun 28, 2012, at 2:44 PM, Hendrik Boom wrote:

> On Wed, Jun 27, 2012 at 02:20:41PM -0500, Rodney M. Bates wrote:
>> 
>> Text is highly general and easy to use.  Concatentations and substrings
>> are easy.  Semantics, to its clients, are value semantics, similar to INTEGER.
>> Random access by *character* number is easy and, hopefully, implemented
>> with efficiency at least better than O(n).
> 
> Does it have to be a *character* number we use to index a string?  I 
> don't know of any situations where that aspect is importnat enough 
> to force everyone to waste storage on it.
> 
> -- hendrik

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20120628/de03e164/attachment-0002.html>