World: r3wp

theoricaly yes, schemes exist under R2 too

do you want R2 version at first ?

BrianH:  ELSE  -  I never used it. I don't care if it's removed.

well at least there is a chance :) .. well I don't know when I will 
be able to try R3 at all, and even less when I will be able to use 
in for real projects... that's why I am asking, but I don't "urgently" 
need it right now so no worries for me

I like that you focus on R3 because this all moves it forward too, 
so hopefully we will get to it sooner than later

BrianH, I first noticed ELSE now that you mentioned it :-) Don't 
need it.

Fixed sized would only be faster in the sense of retrieving specific 
records.  Traversal is actually slower.

But I would say offer it anyway because this would make the virtual 
block scheme more versatile for the respective application.

will R3 have something similar than coroutines or a way to simulate 
cooperative or preemptive (green-not on os level threads) concurrency?

(I imagine that if not otherwise this could somehow be made in libraries 
with its code is data feature)

R3 has tasks, which I believe are OS threads.

wow, really? this is cool.. usually scripting langs have only green 
(not-os) threads

Tasks are very interesting, as it will render slow and large cooperative 
threading libraries for R2 moot. You create a task like you create 
a function and it can be used in the same way, except you are returned 
to the console right after calling it. Also networking is completely 
async on the lower level, which helps speed up network operations. 
You can achieve similar things in R2 through hacks, but it's not 
well documented or stable.

Janko, I can't be completely sure that they will stay that way. This 
has something to do with the Wildman project, which is about getting 
R3 to run standalone on embedded hardware with a minimal OS underneath. 
So whether R3 will then employ its own threading model or always 
use OS threading, I don't know... and Wildman is not something that 
will happen soon.

Tasks are available in the old public alpha, but they may not be 
stable.

what is that project ???? Who is working on WILDMAN ?

well it's very nice to know that something is being developed in 
this too.. cooperative threading and async io is a lot already.. 
if there will be native threads it's just a very big additional bonus, 
(even factor, which is very progressive lang. in terms of core features 
and libs will have os level threads only in version 2.0 for example)

Steeve: I suppose some wild man :)

Steeve, not an active project yet. This was talked about when R3 
went internal alpha.

http://www.rebol.com/priorities.html<-- near the bottom. Just replace 
2007 with... 2012 or something. :-)

[virtual blocks] it would be more convenient to create a new scheme 
for fixed-size records. I don't want double the size of the current 
 scheme just for a new option.
(Most of important actors have to be rewritten)

Ok Henrik, it's only one of the zillions of Carl projects we'll never 
see ;-)

:-)

Have you tried any stress/performance tests on VBS yet?

Not really because one major bug on file scheme block me.

ticket #552 in curecode

Steeve virtual blocks scheme still at megashare? I've bad luck trying 
to download.

give me a convenient place and i post it

I can host it for you.

Steeve, if you paste the code to me privately, I can host it.

you don't have the first version i posted Henrik ?

nothing has changed currently

ok, I'll find it again.

ahah...

http://hmkdesign.dk/rebol/r3/idx.r

I'll post on rebdev too.

THNX 2 U both

ok, thanks

I would not currently assume that tasks will eventally correspond 
to threads at all, green or not. They might switch to the microprocess 
model. In any case we'll try to pick the best strategy for REBOL.

In the french BSS, Carl said that the tasks will not use threads.

*BBS

Yeah, threads have been discredited somewhat in the research community 
lately. Perhaps we could go all out with an Erlang-style green process 
model? That would be fun :)

The current public alpha uses OS threads, doesn't it?

And crashes them.

Almost-public :)

Brian, could you create a sub header in R3/protocols for the virtual 
block scheme ?

Sure.

and move all related msg please (Argh...) :)

Oh... excuse me Henrik, you requested it and you could do that too...

Done.