World: r4wp

Path notation preliminary support added: you can use it on any series 
with integer! or get-word! values as accessors (nested word! values 
need SELECT action to be implemented first).


See changes in demo script: https://github.com/dockimbel/Red/commit/88fd1ff1da855a383e91566903fe373ea4d41eca

Doc, apart from Twitter, please don't forget about using another 
marketing channel - Facebook :-)

Pekr: I try to use each channel for what it is worth for. :-)

Set-path notation support for modifying series added.

Functions refinements support added. /ONLY option implemented for 
MOLD, much more to come soon.

In R3, There are 56 actions, 159 natives, 21 ops, 56 datatypes. Now 
in Red, there are 19 actions, 21 natives, 10 ops, 15 datatypes, respectively.

Just a simple comparison.

DO you need all 56 datatypes, 159 natives. Development last years: 
R3 nil Red exponential just a comparison ;)

There is also the basic work to do, like the lexical scanner, port 
system, etc. Some of the work on actions and natives can be outsourced 
later.

Bad comparison: Active project vs. suspended project.

They aren't even in the same stage of development, as R3 is much 
more mature at this point. This is not a criticism though, as Red 
was years away from existing yet when R3 was at the stage Red is 
at now. There is still much to look forward to from both projects.

R3 has about 190 mezz functions, Red has none so far, which will 
be supported soon.

Hopefully in a way that allows the compiler to not include the ones 
that aren't used, at least for closed apps. 190 seems like a lot. 
By closed apps, I don;'t mean closed source, I mean apps that don't 
execute external scripts, like iOS apps.

Probably not as much of a problem for Red as it was for Delphi though 
:)

Jerry: interesting metrics. You could keep track of it month by month 
and publish them.

He should write a script, one that runs both under R3 and Red. :-)

if Red is reflective enough to do that yet...

We don't have system/words yet nor file I/O...looks like a challenge. 
;-)

Is it possible to echo it? Then you can pipe it to a file.

It should be possible, yes.

You might be able to do source analysis using an external tool, for 
now.

We should have file I/O in a few weeks anyway.

Doc, I will. The metrics will be numbers of 1. Datatypes 2. Actions 
3. Ops 4. Natives 5. Functions 6. Objects 7. Schemes 8. GUI-Components

The completeness and stability of them will be ignored here, which 
is not fair to R3. But like I said, It's just a simple comparison. 
The purpose is to see the progress of Red, not to discredit R3.

You can add those two also, no problem. Red is already more complete 
than R3 on some aspects, like Unicode support.

Also, Red will add its own features, like specific datatypes, natives, 
actions,... For example, MOLD and FORM both have a /PART refinement.

Doc, Unicode in R3 is pretty good for me.

IIRC, it doesn't handle characters above codepoint 0xFFFF.

I write a book for R3 instead of R2 because R3 supports Unicode. 
Without Unicode, R2 is useless in China.

Yes, I've noticed that. By supporting USC-4, Red is better than REBOL. 
But Characters with codepoint > 0xFFFF are rarely used, I think.

I was reading your Unicode.reds earlier, It's really cool to see 
that Red supports UCS-4.

Well, if you look at the astral planes, you'll see things like music 
notes or play cards, I bet they will become quickly as much popular 
as they are useless. ;-)

Many years ago, I found REBOL 2 and liked it a lot, but back then 
REBOL didn't support Unicode, so it was useless in China/Taiwan. 
I wrote e-mail to Carl, but I got no feedback. So I decided to start 
a magazine column in China and Taiwan to introduce REBOL. My idea 
was to make readers love REBOL and felt the same pain (of no unicode 
support). I also kind of encouraged them to write e-mail to RT on 
the Unicode issue.

After a while, Carl said (in somewhere, blog maybe) that he didn't 
know why REBOL had many Chinese users, and they need Unicode. So 
he decided to support Unicode.

Doc, I am glad that Red support Unicode in the first place, so I 
don't have to do the same trick to you. :-)

I remember that Unicode in R3 is mostly thanks to you. :-) No modern 
programming language can miss full Unicode support now, so it's a 
mandatory feature to have, anyway.

For those of us still dealing mostly in pure ASCII will there be 
a 1-byte per character string alternative?

Ashley: Red string! use 1-byte per character by default, so as long 
as you stick to ASCII, it takes the same storage space as C strings. 
As soon as you insert a non ASCII character, the string will automatically 
upgrade to the appropriate format. It's transparent for the Red user. 
Moreover, you'll be able to force string encodings back down to 2-bytes 
or 1-byte when possible.

So, upgrade is automatic, downgrade should be manual.

0-127 ASCII, or UCS-1 (aka Latin1)?

Latin1

Cool :)

So, I should have said "as soon as you insert a non Latin1 character".

In any case, you can always bypass the whole Unicode layer by reading 
(or converting) strings as binary! values, and then processing them 
the way you want (this is not recommended though, but some users 
might need it).

For instance, users converting character encodings to Unicode, encodings 
like UTF8 or national encodings.

Red should provide an UTF-8 codec. For national encodings, we would 
probably proceed by offering  on-demand online codecs for the most 
used ones. That could be a shared resource with R3.

I was talking about the codecs. They need to be written too, right? 
:)

Sorry if I missed the answer to this, but are you going to be doing 
a UTF8 binary parser for Red's source the way that R3 does for its 
source? Rather than a Unicode string parser, which processes the 
source after it's been through a codec?

Yes, that's the "runtime lexer" in Red's roadmap. It is required 
for implementing LOAD (or TRANSCODE if you prefer).

BTW, we already have a UTF-8 binary parser in the Red compiler.