World: r4wp

I think we have a ticket about that TO error ignoring problem.

Brian, it's not an error. TO/THRU support integers.

Andreas, you're right! That's a great feature!

to [2] should work, to 2 shouldn't.

But when to 2 doesn't work, TO doesn't complain.

Why it shouldn't work? It's great.

https://github.com/rebol/r3/blob/master/src/core/u-parse.c#L487

>> parse "abcdefgh" ["abc" to 2 p: (probe p)]
bcdefgh
== false

>> parse "abcdefgh" ["abc" to 7 p: (probe p)]
gh
== false

Rebolek, unfortunatly, you are mis-using TO.   TO is a search.   
 what you are doing is supposed to be done with SKIP

Is there a skip operation in PARSE?

Maxim: SKIP does relative positioning, TO/THRU do absolute positioning.

Well, that behavior seems like an undocumented feature. And a useful 
one :)

Wait, that's right, 2 skip, not skip 2.

what? heh? yuk.  sorry, but how do I then search for integers?

to [2]

I find that becomes quite assymetric in use.  if TO is going to change 
behaviors... relative in some cases and absolute in others... using 
weird datatype conventions (which seem to be completely different 
from the rest) then I'd rather have a new Absolute keyword which 
works just like to on All datatypes.

just like TO 2 ,  but on All datatypes.

Only what would `absolute #"a"` mean?

Move to Parse if this applies to R2 as well.

Applies to R2 as well, so let's move to "Parse".

Andreas, did you discover this by just playing with parse or did 
you read through the source? I wondering if there are other goodies 
in there.

Reading the source.

But this was pretty much the first thing I started looking at, which 
already lead me down the rabbit hole of testing it in R2 and R3, 
looking for documentation, filing a documentation request against 
R3 and discovering and reporting a bug against R3 (and I'll probably 
continue down the hole and fix that bug). So I didn't get much further 
towards other goodies, yet :)

A worthwhile hole, me thinks.

Guys, was there any discussion about the COMPRESS/DECOMPRESS natives 
in R3? Do we really need these functions to use some 'custom' compression 
format that noone in the world uses and when it is based on zlib 
anyway? Wouldn't be better to change this in R3 and use for example 
ZIP format? What do you think?

I remember Carl saying the custom format is more efficient but I 
tried to compress couple binary or text files to compare with ZIPped 
results and I don't see any significant difference that would be 
worth the current format incompatibility.

Earlier discussion of COMPRESS vs Zlib.....Basically, the two are 
almost identical already, so it should not take much to make something 
that is compatible:
     http://curecode.org/rebol3/ticket.rsp?id=328

I agree that it should be easily compatible with other compression 
formats, but it does not take much to make it compatible (can be 
done via a mezz).

Sunanda, thanks for the link.

Henrik, I was more thinking to rip the old zlib code out of Rebol 
and put there some more actual(or even smaller) implementation (latest 
zlib or miniz etc.)

maybe, historically, also the licence was a problem? Remember, R3 
was not open-sourced back at that time ...

I am fully for new, more standard way. I e.g. did not like .RIP format. 
E.g. Winamp uses normal zip format for their skin modules, etc. I 
would like to just hit enter or double click, getting into the archive/package.

Cyphre: that sounds fine to me.

Pekr, I don't think .RIP was meant for basic temporary compression, 
but a more fully fledged file format to store serialized REBOL data 
efficiently?

Henrik - RIP was crap :-)

I would prefer my app being packaged in default zip anyday ...

For me it was just another way of reinventing the wheel, with almost 
no added value ...

Pekr, I don't think it's the same thing, plain and simple.

Would you not want a single, universal way to store and retrieve 
application state from disk? ZIP does not do that.

why not? Because you can just 'do the .rip? I would not mind do decompress 
%my-app.zip :-)

Well, then I am wrong, ok. Not sure .rip format was anything in common 
with app state serialisation. I thought it was just plain and simple 
packaging mechanism - having a header, and binary container for compressed 
app modules/scripts ...

Zip does not manage bindings or words transparently. It's simply 
not the same thing.

(and if it turns out, that it was not the goal with .rip, then the 
goal should be changed to do this)

Then we talk two different things though. But - don't push anything 
like .rip on me, just to package my app. I want more transparent 
way, a zip archive I can inspect in Total Commander, Windows Explorer, 
etc.

I would not want that a requirement for .rip anyway.

If you want something modern, add support for LZMA compression. And 
please don't mix compress with zip - zip is high level, compress 
should be low-level function (idealy supporting more formats)

Oldes - we don't mix anything. It was zip vs rip discussion. I say 
- let's .rip RIP :-)

regarding zip versus rip - I can imagine runable zip - just add special 
file in it which would be used as a starter - actually that's how 
works for example APK, which is zip with different extension.

I say - let's .rip RIP :-)

 - how can you say this, when we want a way to store application states?

store them in zip, simply some storage format inspectable from other 
tools. I still don't understand, what is so special on rip, it is 
imo just a storage format, nothing special.

Pekr, there is a lot more to storing application states than simply 
zipping data.