World: r3wp

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.

Implemented seekable i/o in the C library binding

We had some tea at Hekovnik (hackerspace) and one very experienced 
programmer here started talking about new language Red .. I was what?? 
Did you say Red :) .. he read about it on the OSNews

:-)

Did he have an opinion yet?

You'll note that only a few trolls have responded to the article, 
and one person who already knew REBOL. This is typical when you introduce 
something that people don't understand. They'll hold back from responding 
in fear of saying something that makes them look stupid. However, 
so far four thousand of them have traveled from the article to the 
Red site, which is more than we get on a typical Syllable article

He was interested about it all so I hope Doc's (and comunity's) progress 
will go well. ( BTW: Doc, He also noted you have a little familiar 
name ;) )

I will try to chip in once you get to more app / lib level :)

4K of visitors? Nice.

A question is being asked about the JIT on OSNews.

Janko: cool news :-)

Kaj - what is your take on the Red & Syllable? I mean - Syllable 
is open-source. You used Boron for some stuff, and then you thought 
of using R3. Are you now thinking about the switch to Red?

About the LLVM question on OSNews, someone with an account there 
could anwser by posting this link to a similar question on the Red's 
ML: http://groups.google.com/group/red-lang/browse_thread/thread/eeca0a4787da56c2?hl=en

And maybe few questions to Doc:


1) R3 got some stuff as codecs (not yet implemented) and devices 
for async. Will you think about such abstractions too? (e.g. ports), 
or is Red going to be more "straighforward"/traditional?


2) as View is mostly open-sourced too - will event system allow to 
eventually port View engine to Red later?


3) as 2) requires 'parse, do you plan to have kind of R3 parse too? 
Is that even possible? (as Red is not so dynamic as REBOL?)

1) Ports and devices: yes, definitely. What features does exactly 
"codecs" cover in R3?


2) I was not aware that it was allowed to use View sources with anything 
else than R3?


3) Parse: absolutely. Not sure yet if it will be 100% compatible 
with R3, but it will at least, support R2's whole parse dialect. 
Red should be as "dynamic" as REBOL for the code<=>data paradigm 
once the JIT compiler will be in place.

View sources: If it's BSD licensed (essentially) what would prevent 
them from being usable elsewhere?

If View sources are available under BSD, I will be glad to have it 
as one of the possible libraries for making GUI apps.

I will ask formally.

Petr, it has been a bit of a process in my head in the past few months, 
but to be honest, I've decided to move all my R3 developments and 
plans to Red. All of those also apply to Syllable

I've been waiting for a decade to be able to use REBOL, because it 
never ran on Syllable, and for the past half decade, all subsystems 
were planned to be replaced, seemingly making it uneconomical to 
start using R2 on other platforms

In the past two years I made a lot of effort to get R3 running on 
Syllable Server and then Syllable Desktop, and just now that it was 
becoming somewhat usable, it's being abandoned

This after going through the Atari trauma, and having decided never 
to do that again, seeing all those other people go through the Commodore 
trauma, the Amiga trauma, the RISC OS trauma and the BeOS trauma

I made an exception for REBOL because it's brilliance couldn't be 
found anywhere else, and I paid dearly

Kaj: thanks for your answer to the LLVM comment on OSNews.

Hope I'm saying it right

Yes, it is nicely summed up.

The Rebol source headers say .. free to use as long as you keep the 
headers intact.  And then refers you to the full license .. whereever 
that may lie.

Are the View sources complete in the host-kit or are some part of 
it sill buried in the closed Core?