World: r3wp

native, at least that was the idea.

personally i somewhat prefer soft, but native has the advantage of 
making use of multiprocessor machines.

I agree... and with dual cores becoming increasingly main stream... 
there is a definite advantage in that.

i don't know if it will be easy to use native threads across all 
platforms though.

hehe if windows didnt design "kill a task" from inception... I can 
only imagine how well its threads must be implemented.  <sigh>

although they require very little RAM IIRC

unix is probably not that great on threads either, i think everyone 
is using their own variant.

there is a crossplatform library iirc, i hope it works :)

Threads are actually done very well on Windows. They also have a 
fast shared-memory thread-like thing called fibers. It was only recently 
that some of the Unixes were able to catch up (except Solaris, which 
may be better).

Windows sucks at processes though.

(BTW, I meant that Solaris may have been better than Windows at threads 
already. Stupid English.)

Please refrain from calling we English stupid ;-)

Just teasing

brian, my fear is having differences across platform. the complexity 
can go up very easily, especially when there are platforms that support 
threads badly.

i hope that, as you say, most unixes have catched up at this point...

then Carl should look for very small kernel to license, which solves 
that - e.g. QNX - it has 75KB kernel IIRC :-)

I really wonder, what R3 will be about - tasks (threads), new event 
system ... when thinking in cross-platform terms ...

Linux and all of the commercial Unixes are good at threads now. I'm 
not familiar with the BSDs.

OpenBSD and FreeBSD have very good support for them. NetBSD is lagging 
behind. DragonFlyBSD has even better threading model.

http://www.plausible.org/nasal/

http://wiki.flightgear.org/flightgear_wiki/index.php?title=Nasal_scripting_language
Nasal - small, os-threads, used in flightgear.

Maybe the treading is usefull?

anybody able to find good  names for zero-based index series functions 
like variants of PICK, POKE, etc...?

(any other any zero-based indexing suggestions welcome)

peekus and pokus - more like ancient Latin language roots...

pokus
 means "trial" in Czech

zpeek, zpoke ?

Didn't we have this kind of discussion with rebcode ?

cee caw

what's the logic behind that, Tom ?

four days of fever and chills
that and c - zero based arrays

(the latest names are PICKZ and POKEZ, but I am not sure they are 
acceptable)

I'm not sure we can do better, Ladislav.

Tom, hope you get better.

me too

Three letters start to look a little bit cryptic. Reminds me of LISP's 
car, cdr, cadr etc.

get and put

suck and blow

long thread on that subject on the ATM (amature telescope maker) 
list, to put   fans in front of or behind the mirror

slurp dump

get / set  I think would be my choice it is already in common use 
for similar ops

I think Ladislav is suggesting that, in addition to the existing 
PICK and POKE, which are 1-based, we add two new words which use 
0-based indexing.

yes   get/set  for a   0 based series seems reasonable at the moment

suck and blow .... LOL  !

zick, zoke :)

if you really use 0based, you know what you do, an can remember that. 
and it sounds dynamic :)

will we need a 'zeroth too?

can it be a long name?
  pick-before series 27
is what it does.

could we define hair as being before head   ?  ;-)

I would use z-pick/z-poke rather than pickz/pokez. It mentally expands 
to zero-pick rather than pick-zero, and reads as zee-pick rather 
than picks.

or rather pigs