World: r3wp

If it was committed before the last few hours, I have it

Is that not in the trunk branch? Then I don't have it

I have merged it in main branch 2 days ago.

Two days seems like a long time ago. :-) If that was the final fix 
for 0MQ on Linux, then I already had it

But that was earlier, wasn't it? Then I have only tested the latest 
callbacks with cURL

Right, it was the final fix for callbacks (for the 0MQ issue).

Kaj: we have decided to replace the "struct" and "pointer" by "declare". 
Please read this post: http://groups.google.com/group/red-lang/browse_thread/thread/9c407676e2335919?hl=en

I will be waiting for you to upgrade your bindings before making 
the announcement (hope we can do it tomorrow). I have some things 
to add in the specification and red-lang.org site to dust off in 
the meantime (well, tomorrow would be nice ;-)).

I just checked that all the bindings still work with the current 
Red, so the syntax should be the only thing left to change

Ok, if I merge it now with the main branch, can you make the changes 
shortly after?

Definitely

I will wait until tomorrow to make the announcement anyway.

Ok, doing the merge...

Merged.

Going to bed now, will update the web site tomorrow and post an announcement 
on the blog.

(tomorrow => later today)

Ehm, my bindings still work :-)

I only had to make a few changes to the example scripts

This either exposes my preparations for thread safe code, or the 
fact that I haven't written any substantial applications yet :-)

I've extended the read function in the cURL binding to store a file 
being received directly to disk, instead of just printing it

Like sending directly, this has very low memory use

I've confirmed that the Empty and Hello examples still run on Syllable, 
but the cURL binding currently segfaults

I've confirmed that the bindings still work on Windows, at least 
on WINE

The cURL binding seems to work there, too

Thanks for all those tests.

Kaj, do you have gdb on Syllable? If so, please run the curl example 
via gdb and add the output of "backtrace" to the bug report. Thanks!

The last reports were that GDb doesn't work anymore, but I'll try

http://www.red-lang.org/2011/07/redsystem-goes-beta.html

http://development.syllable.org/news/2011-07-05-02-54-Red-System-programming-language-now-beta.html

wow, that is fast development!

Absolutely!

I wish it could go faster. :-)

Wow! veeery nice news! Thanks guys!

really good work guys!

http://www.osnews.com/story/24921/Red_System_Reaches_Beta_Loads_Syllable_Shared_Libraries

hehe, again on OSNews! Thanks Kaj!

My pleasure

As long as you keep Red relevant for Syllable, I can get it on OSNews 
;-)

Sounds like an invitation to rapidly fix the cURL binding issue. 
;-)

Yeah, it's a tricky one

I was going to ask you if you considered sending the beta to plnews.org, 
but it seems to be gone

If you can provide a minimal example exhibiting the issue, I should 
be able to locate the problem from the disassembled code.

I will make post a news on freshmeat.net tonight (I still have some 
things to change on the web site).

I'm not used to working at that low level, so I'm moving a bit slowly 
on it

We're becoming popular. The trolls are very quick to respond now

:-)

http://development.syllable.org/documentation/introduction/part-1.html

GDB on Syllable currently only supports real-time debugging, as crashed 
applications do not generate a 
core" file (crash dump)."

If GDb still works, I guess that prevents me from getting a backtrace

The kernel log is probably the best backtrace we can get