OpenEuphoria

Re: compression beta, and BIG bitmaps

• Posted by tone.skoda at siol.net Feb 23, 2002
• 436 views

An Euphoria library could be written to have sequences (or arrays, better
word) of bits (1 bit), bytes, chars (8 bits) and shorts (16 bits).
If you have sequence of 0's and 1's in euphoria now it takes 1000 bytes for
1000 elements. With such library it would take only 32 bytes (1000 / 4 / 8)
for same 1000 elements, only 3% of size! In integer type can be stored 32
bits or 4 characters, so strings would be 4 times smaller if saved in such
array.
Now euphoria sequence has allways 4 bytes (=32 bits) for one member, that's
a waste of space.
This library could be written using bits_to_int () or and_bits() and that
stuff.
Libraries to have arrays of bits in C were already written, so that 8 bits
are saved in 1 byte, not 8 bits in 8 bytes.
You would have to use get_member () and set_member () functions for such
array, not [].

----- Original Message -----
From: "Wolf" <wolfritz at KING.IGS.NET>
To: "EUforum" <EUforum at topica.com>
Sent: Saturday, February 23, 2002 5:49 PM
Subject: Re: compression beta, and BIG bitmaps


>
> <tone.skoda at siol.net>  wrote:
>
> > I'll take that back. I tried it with 75 MB bitmap - it works slooow.
>
> < chuckle >
> I can imagine !
> A 75 MB bitmap would translate to 300 MB of Euphoria 'sequence' just for
the pixel data !
> Four bytes/byte... with a *lot* of disk swapping, no doubt.
> The "Remove Colors" option is, in any case,  the slowest part of the
program, and almost useless for bitmaps of more
> than about 32 KB, since a 256 color palette is only 1 KB to start with.
>
> Wolf
>
>
>
>