World: r3wp

Won't have time tonight for a debugging session, will look into it 
later next week.

syscalls will probably be gone soon anyway :)

How is that?

i think we'll switch to libc once dynlinking works for elf

You'll still need prolog and epilog syscalls, and I think Doc wants 
to minimise libc usage

I agree that it's almost unavoidable, though

what prolog/epilog syscalls?

exit for example

why not use libc exit?

Ah, you're right

Anyway, I do greatly value the capability of syscalls. I'll also 
need them for close Syllable integration

certainly, they'll still exist

http://bolka.at/2011/tmp/world.bin

a red-generated dynamically linked binary, if someone wants to try 
on syllable :)

requires libc.so.6, calls puts and exit

ah, ignore that. need to add the alignment fix to that first

http://red.esperconsultancy.nl/Syllable-readelf-a-link.txt

link is almost the smallest system program, apart from false

It's still 15 KB. There's a lot of GNU junk in there

Doc, the newest Syllable browser offers to download the executables, 
so it's probably a problem with the older browser. The new one is 
on your live CD, not in the 0.6.6 release

Red programs currently indeed pagefault on address 12345678

Ah, I was advised incorrectly. exit is not syscall 5, but 6

5 is indeed Fork, which crashes now

I uploaded new binaries

Congratulations, no more segfaults :-)

Yep. Thanks very much, guys. I'm very pleased with this

While you're in Lille, keep an eye on OSNews :-)

Starting Red presentation in Lille France since one hour.

Follow us on Twitter : #redlang_france, #red_chronicle, #rebol_france, 
#olivierauverlot

Nenad thanks Peter for his contribution to Red : QuickTest

I've bound most high level input/output functions in my C library 
binding

So Red can now handle files

It's mostly untested, so let me know if something doesn't work

Implemented block i/o and status handling

Implemented low level byte and line i/o

http://www.osnews.com/story/24798/New_Red_Programming_Language_Gets_Syllable_Backend

Sorry guys. I worked through Friday night to have the article announce 
Lille, as well, but OSNews didn't process anything since Friday evening

OSNews: it is fantastic to be mentioned there, thank you very much 
Kaj!

The article is very well written and it is the best introduction 
to Red I have seen so far.

Nah, yours are better. :-) I'm just placing it in a context for Syllable 
and OSNews readers

If you can't think of anything to do this Sunday, you could watch 
the page counter on the Red site :-)

He he :-)

Wow, you're right, 800 page views in 3 hours!

The US are still waking up

Ah, people voted down the troll

French presentation of Red programming language available on http://www.red-chronicle.com
| Documentation

The resulting value type for math operators is the type of the left 
argument (an implicit type casting is operated when required).

What motivation lay behind this?

Implementation constraint for + and - to support pointer/struct/c-string 
arithmetic without having to explicitly cast the 2nd argument. So 
to avoid having a different rule for * , / and //, I chosed to let 
the implicit casting occur on all math operators. But as the implicit 
casting is reducing the safety of expressions, I might make it more 
strict than it is currently.

Will you add floats to Red/System? Will 1 + 1.5 then yield 2?

Floats in Red/System: depends if Red would rely (fully or partially) 
on Red/System's code emitter or have its own one. If Red/System gets 
floats, such operation might be authorized too. The implicit casting 
would do a ROUND/DOWN conversion, so additional rounding functions 
will need to be supported too.