OpenEuphoria

Re: Str-Kat

• Posted by Kat <KAT12 at c?osahs.?et> May 30, 2008
• 705 views

Shawn Pringle wrote:
> 
> Kat wrote:
> > 
> > Shawn Pringle wrote:
> > > 
> > > Kat,
> > > 
> > > A EUPHORIA string is a sequence that contains integer
> > > values that each represent a character value.  EUPHORIA
> > > has a string type as much as C does.
> > > 
> > > A string is not dealt seperately as a special type and
> > > it doesn't need to be.
> > > 
> > > Unlike both BASIC and C though there are no special
> > > string ops that concatonate, determine the length, and
> > > copy.  In EUPHORIA you manipulate strings and arrays 
> > > the same way because they are the same.  They are all 
> > > sequences. And since sequence manipulation is strait 
> > > forward so is string manipulation. I wouldn't want 
> > > it to be any other way.
> > 
> > Really? Since when does EUPHORIA use only 8 bits for each CHAR in the
> > SEQUENCE
> > ? Since when can you load a 500mbyte STRING into EUPHORIA and not have the
> > OS
> > kill the application with "too much memory used" error (windoze allows each
> > app to have  only 2 gigabytes)?
> > 
> > Kat,
> > forgetting she wrote STRING-TOKENS lib in archives.
> 
> I didn't say 8 bits for each character.  Normally they are 7-bit but for
> those who are doing non-English they could be 18 bit.  Frankly, I don't
> give a damn.

There's the problem. Doesn't explain why you brought it up tho.
 
> Why would you want to load a 500 MB string into memory at once anyway?

You going to criticise the "why", instead of finding the "how"?

Ok, try loading 250 megabytes and *using* it. The 250 will become a gigabyte,
and almost any way you use it will copy it, making it 2 gigabytes, and the OS
will kill it.

Oh, for non-ascii chars in non-usa places, you could still have UTF-8 or UTF-16
strings and still save memory. Your example still used 32bits/char.

Kat