Re: zip etc
>David, Ralf & Co
>(Sorry, David, for lumping you together with the other one), apart
??! I really am confused what I should do with remarks like this. All I do
know, is that it isn't me that's insulting some1 this time.
>from the nauseating OO discussions, we seem to be getting only a
>fairly steady stream of resource managers, binders and special
>compression routines. Call me a wrecker, but I still do not get it,
>and I read the docs!
I suppose you meant my EDOM library is not needed at all, cause we can zip.
Well, the point is not compression, or binding files together, the point is
we can now easily (read: fast, safe, simple & efficiently) store a sequence
containing any type of data.
Euphoria enables you to manipulate data, without having to specify the
datatypes, there range, etc.
But you couldn't easily store data to disk, without knowing the format of
the data preciously.
EDOM interpreters the format and stores both the format/structure and the
data to disk.
You could do this with print () get get(), but get() is *very* slow and
speed inefficient. Print () however is fast because it is a built-in
routine. However do you want { "ABC" } to be saved as: { { 97 , 98 ,
9 } }. 1) It looses its readability for text anyway. It loads back up
very slowly and it takes huge amounts of harddisk.
Imagine a complete database in a sequence, can be saved with one command.
Highscores, sprites, etc. don't need special routines to load or save them.
I hope this explains its usage to you.
If this too doesn't help, then maybe you don't want to understand it, maybe
due to some personal confict, eh... Jiri ?
Ralf
|
Not Categorized, Please Help
|
|
