OpenEuphoria

Everyone,

this has been talked about already. It isn't a new idea at all. It was Kat complaining about the same thing. It seems rather inefficient to store bytes into 32 bit words. Then by using astronomical sizes you see the size is too big in memory.

A solution was Kat Strings. You add another field to the s1 struct in the EUPHORIA internals that describe how data is stored in a sequence and by making the C code a lot more complex you could save space in this unlikely scenario. The price of which is more code in the backend and more cases and probably more complex translated code as well...

Then, why would you need to store so many bytes in memory when we have mysql and a like?

Shawn Pringle