World: r3wp

R3, will allow us (finally) to merge rebol INTO other stuff, so it 
can become the controler for lower logic, but when that starts, people 
will usually start writting everything in rebol... cause its just 
plain productive.

like Lua .... but ppl will say but Lua already do it and it's better 
damn people ...

Ever tried to use rebol in a company that has only .net, python, 
or java code?  good luck.  it takes weeks before you can use most 
of the DB stuff they have built up, because there are sooo many modules 
out there, and they have huge frameworks, which actually DO more 
stuff than rebol .  rebuilding those libs is not even always possible....

ex  integrating DirectX/OpenGL into view... nope.  loading dll classes... 
nope... etc, etc, etc.

but R3 will change all that  :-)

http://www.rebol.net/r3blogs/0194.html

SELECT/SKIP behavior discussion needed now.

comment posted i don't know if that will make any sens ...

select/skip b 3 returning 20  only is an aberation ... that's not 
what we expect ...

It's what I expected, but I've never used SELECT/skip in R2. The 
R2 behavior sounds better to me.

It sounds silly, but after 9 years there are still parts of REBOL 
I've never used :(

but the skip becomes pretty useless, as you can get the inner records 
of the skip.

BrianH hum same for me ...

the /skip in many functions are implied records... and the reason 
they are there... not getting the record as a return values... is 
an oxymoron IMHO

I still discover new functions after 9 years too  :-)

Maxim, are you in favor of the R2 behavior or the current R3 behavior? 
Or something else?

R2

the R3 return sort of alleviates the point of the /SKIP refinement 
no?

So am I. I wasn't saying I preferred it, just that I expected it. 
I think this is why I've never used select/skip :(

The R2 method is much more flexible. The R3 method is identical to 
"first select/skip", and I doubt there would be that much gained 
by having a specific alternative function for the R3 method.

I prefer the R2 method
 - I bet noone expected me to ever say that :)

BrianH, not working much with flat blocks, eh?

its like sort/skip there is a simple consistency in the implied records 
which I always like... other languages will have a framework just 
for that...

brian: LOL

I tend to use FIND and SET [w1 w2 ...]

but find will trip if records ands content can have the same datatypes... 
wich is why the /skip refinement makes sense.

(for select)

Sorry, FIND/skip

Maxim, yes. I'd say that if every single REBOL function used /SKIP 
consistently, you could do flat block databases and rely on /SKIP 
without getting your records screwed up.

its almost the case now... sort/skip  find/skip  select/skip

hey, here's a fun one:

a: [1 2 3 4 5 6 7 8]

select/skip a 5 -4

hangs.

which function is fundamentally different in this regards ?.... I 
don't seem to recall one off the top of my head

(in regards to /skip)  post order makes my last post a bit out of 
context

Henrik, is that in R2 or R3?

R3.

I noticed something weird too. If you have multiple R3 windows open 
and switch between them, does the window title change?

select/skip issue submitted to curecode.

The window title thing seems to be related to marking up text in 
the console and is not caused by R3. Never noticed that before.

it seems FIND/SKIP does the same thing. :-)

Alpha 50 released.

7 reports with /SKIP issues.

Clearly we are going to need a /SKIP doc in R3/Language/Options.

Agreed.

I wrote MOVE, so talk to me. How should MOVE with negative skip work? 
Allowed or denied?

I don't really know. I guess we want consistency?

From what I can see the correct way is to provide an out of range 
error on less than zero.

move is like next but modifies the series itself?

We don't have consistency, so I figured I'd start with a fuunction 
I understand.

should say move is like skip

No, move actually moves stuff.

move: make function! [[
    "Move a value or span of values in a series."
    source [series!] "Source series"
    offset [integer!] "Offset to move by, or index to move to"
    /part "Move part of a series"
    length [integer!] "The length of the part to move"
    /skip "Treat the series as records of fixed size"
    size [integer!] "Size of each record"
    /to {Move to an index relative to the head of the series}
][
    unless length [length: 1]
    if skip [
        offset: offset * size: max 1 size
        length: length * size
    ]
    part: take/part source length
    insert either to [at head source offset] [
        system/words/skip source offset
    ] part
]]