World: r3wp

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

real-time debugging
 should be fine.

(unless that means something different than i suspect it does.)

1. compile a binary using red as usual
2. instead of running the binary directly, run it via gdb:

    $ gdb builds/hello
    (gdb) run

3. when the program segfaults, you should be back in gdb
4. print a backtrace using "backtrace":

    (gdb) backtrace

The problem with the current GDb on Syllable is that it doesn't know 
how to load shared libraries, so it can't load cURL

backtrace says it has no stack

The issue with shared libraries seems to be limited to the fact that 
cURL can use libdl. I don't know what was different now, but I got 
a GDb trace. Will put it on the tracker

The crashes seem to happen when cURL calls the C library, so outside 
the Red program. I'm not sure it's useful to disassemble a minimal 
Red example

I have 37,000 followers in Sina Weibo (aka Chinese Twitter), Most 
of my follower's are programmers. I've just mentioned Red in Sina 
Weibo. I hope that will make Red be noticed in China. I would like 
to thank Dockimbel for Red.

Jerry: thank you! 37k followers, that's huge!

silly question: is it possible now to build a CSV parser in Red?

There is no Red yet, only Red/System which is a low-level dialect. 
So, yes it is possible, but there's no special feature that would 
help you much for that task.

ok, I was just looking into the idea if it was possible to build 
one with better performance than what I currently can.

It will probably be much faster than the one you could write in REBOL, 
but you'll have to do all the memory management manually.

ok, thanks

The parsing functions in the C library binding can get you halfway

Got the cURL binding to work on Syllable, starting from Andreas' 
example. :-) Will research some more and report on the tracker

Good news!

just found this... it could be a good reference for low-level bit 
handling in Red.
  

though the code is in C, its probably easier to understand this way 
and convert to Assembly after (when no comparable machine instruction 
exists).
http://graphics.stanford.edu/~seander/bithacks.html

it has soooo many variations and its been thouroughly tested and 
analysed by thousands of people.

good sauce

Bookmark: "Calling conventions for different C++ compilers and operating 
systems" 

http://www.scribd.com/doc/51814542/36/Relocation-of-executable-code

Right link should be rather: http://www.scribd.com/doc/51814542/calling-convention

And straight from the source (I think we already had this here in 
the past):
http://www.agner.org/optimize/calling_conventions.pdf