World: r4wp

The 0MQ binding also has some documentation there

Actually, the 0MQ docs there include a guide for Red/System, but 
the cURL docs include programming documentation

There are also the materials from the DevCon:

http://devcon.esperconsultancy.nl

Including videos about Red installation and the bindings:

http://www.youtube.com/playlist?list=PL3926D5E4DBD8B360

More than I thought, really :-)

Guys, we will really, really, need something like: http://tour.golang.org
or http://tryruby.orgfor Red.


If someone is willing to start working on such tool, that would for 
sure greatly contribute to the success of Red. I have already bought 
the following domains for such kind of use:

- tryred.net
- redtutor.net
- red4.us
- red2.me

We could even already use Topaz for building it (maybe just adding 
a thin Red dialect on top of it?).

Agree something is needed ... there is no easy guide to get started

Graham: I was thinking it could be ready for end of year of beginning 
of next year. Currently Red is not for end users, and won't be for 
a while. Red/System could be used in production though, but I don't 
have time to write users docs or tutorials for it.

of beginning
 => "or beginning"

Don't we need to wait a bit for more functionality from red before 
writing user docs?

No, you can take REBOL as a model, all basic features will be identical.

We could then upgrade such docs later with Red's specific additions.

Who implemented Try REBOL? Was it Kaj?

http://tryrebol.esperconsultancy.nl/

So - we have something to start with, no?

I'll most probably add Red to TryREBOL. I need to integrate it in 
my CMS, anyway

The next step would than be to get the REPL for Red.

This is to try more Red beyond the things that are save to allow 
on a webserver/browser.

Is it necessary for a tryred to have Red be able to process cgi on 
the webserver.

The easiest way would be to use Topaz and "just" add a Red-to-Topaz 
converter.

That sounds like a lot of work. On TryREBOL, Red and Red/System will 
be used directly

Agreed. Also a great introduction like http://learnyousomeerlang.com/
would help using the REPL and compiling Red.

Kaj btw length-of is scaring me ;)

Is English scaring you?

There are OS- prefixes left in all platform files except Windows

I meant the discussion about the -of postfixes. :-)

Kaj: fixed.

More scary discussion of -of: http://issue.cc/r3/1818:)

Red is now Unicode from end to end: http://t.co/FR8vNV65

Cool!

And with string auto-scaling from 1 to 4 bytes per codepoints. ;-)

*codepoint

I will publish the new code tomorrow.

UCS1 to UCS4 scaling? Fixed-length internally?

Yes, Latin-1 / UCS-2 / UCS-4

Conversion for printing in UTF-16 done on-the-fly (no additional 
buffer needed)

Brian: you don't read Red's blog? :-) See http://www.red-lang.org/2012/09/plan-for-unicode-support.html

Been busy :(

Will you eventually be doing the same trick R3 does of keeping its 
symbols in UTF-8 format internally, for binary hashing? Of course 
you might be handling symbols completely differently...

The symbol being the string part of a word.

Yes, I currently keep an UTF-8 version in cache for each small string, 
but I'm not sure I will keep it.

I'm not using currently hashing for words, but indexing as lookups 
are done mostly during compilation.

I'm talking about eventually, when/if you get real runtime word types 
:)

Words dynamically created might need hashing though.

Right, it could be a good option.

I think that R3 stores symbols in something like a BTree.

Red stores them in a block! value currently, so probably the less 
efficient way...we'll see in the future how to optimize it the best 
way.