World: r4wp

and concurrency? Kind of what Carl have planned? Don't remember where 
he briefly described it, but we once pushed him to say few words 
about it on Altme? Or maybe you plan on more lightweight solution, 
like green threading?

So far, the plan was to use Actor abstraction, but I might decide 
to use a more lightweight approach (something like goroutines). The 
basic idea for the low layer is to have cheap concurrent threads 
of execution that are dispatched over a limited number of OS threads. 
On the upper layer, they might appear as task! or actor! values, 
that you could create in various ways (do/task, read/write on I/O, 
...).

I also have a few ideas about specializing CPU cores in order to 
avoid costly context switching, but I need to test that on paper 
first.

It would be nice if we had something like apt-get to fetch and update 
both yours and 3rd party software

We'll probably have something like an "import" function that would 
work locally and remotely from an organized online repo.

Gregg: thanks for that. I'm all ears if someone has a solid proposition 
for that. I'm even ready to relocate myself in a foreign country, 
if that can help. :-)

I've sent money to europe by bank wire, and it's very expensive. 
 Best if you can setup a US bank account when you're next visiting 
the USA ( if that is possible for non residents ), or an E*trade 
account.

hello is still out of memory on Syllable Server, at a slightly changed 
address

Please try again, pushed a fix a few seconds ago.

42!

Welcome to the club :)

Many thanks

Now for Syllable

Odd that it worked before on some Linuxes

Race condition on return value from mmap call. If address was too 
high, it was failing the safety check (testing for negative values) 
and wrongly triggering the error. ;-)

32

Runtime Error, unfortunately

Not bad :-)

Will see that tomorrow, bed time here...

Night

I'll tell Bas to schedule a Red presentation at Software Freedom 
Day coming week

I'm not coordinating with Nick yet, but will when the time comes.

Kaj: great! Let me know what feature/fixes you need for the presentation!

I'm very, very happy to announce that Red now works on Syllable Desktop 
0.6.7

There's not much in Red yet, so to have something to show I'm going 
to test my Red/System bindings from within Red

For the tech crowd I'll show some of the inner workings of Red

Congrats Kaj!  It's so encouraging to see so much daily progress.

Sure is :-)

Kaj, great! I'm looking forward to watch the videos of your presentation. 
:-)

I can also tell the number of commits has been high this weekend.

Weekend is not finished, expect some more. ;-)

Finally got around to cloning Red from github and doing the test 
system and Red compiles. I hadn't done so since changing machines, 
so it's great to have it all work the first time out. Great stuff 
Doc.

Thanks Gregg, a lot more to come in the next weeks!

is there a list of any-function!s implemented?

Not yet Henrik, I plan to make one of the planned/implemented one 
starting from the official first alpha of Red (at v0.3.0 release). 
Actually, I plan to do this in 2-3 weeks.

*ones

Also, if someone is willing to make such a list right now and maintain 
it updated, that would be nice.

You just need to screen through %runtime/actions.reds and %runtime/natives.reds 
for changes. You could even make a short script to notify yourself 
when those files are modified using github's API. ;-)

It's very problematic to use existing Red/System code in the Red 
#system directive, because it mustn't conflict with any of the internal 
implementation of Red

Wrapping it in extra contexts doesn't help, because #define's and 
other things are global

Even if I wring the bindings around it now, it can break any moment 
when Red's implementation changes

The website needs an introduction/instruction section and a downloadlink 
to a zipped version of Red souces, so people can skip the github 
stuff.

+1 Arnold, although Github does provide a zip download link.

Right, that's new I guess. How many K's is this source now? Ah only 
289 KB couldn't even blink my eyes while downloading it, so there 
will be no real bandwidth issue, I can host one download link on 
my site as well :-)

So - just link red-lang.org to the zip archive? Doesn't it have a 
static/non-changing link?

As I see it, it is available under https://github.com/dockimbel/Red/zipball/master

Kaj: I might make macros context-sensitive, but I don't see what 
more I can do. The point of #system is to write Red/System code within 
the 'red context, so naming should be done carefully to avoid conflicts. 
But with a few context wrappers, you should be able to solve that, 
no?

does it work like a preprocessor or what? Any example, of how is 
Red/System code inlined in the Red?

why not do it like a Rebcode? make red-system ...., or make native! 
.... etc.?

# char should not be used for anything else but - preprocessor. And 
if it works like a preprocessor, we should stop talking about the 
ability to use inlined Red/System code anywhere in the Red source 
code ... :-)