World: r4wp

Nice features of the new macro support: 


- the replacement in the argument block operates for any block series 
(includes paths types)

- nested macros in macros are resolved


- you can define the argument as paren! instead of block!, and paren! 
will then stay once macro resolved.

Here's a more complex example:
    
    #define MIN(a b) [ either a < b [a][b] ]
    #define MAX(a b) [ either a > b [ MIN(p/a p/b) ][p/b] ]

    p: "Hello"
    print MAX(2 1)

outputs: H

(in fine, MAX(2 1) resolves to: p/1)

Nenad, thank you for the explanation. Good to know even the simple 
test works both ways, and I am a programmer not a tester ;)

New macro system pushed online in the v0.3.0 branch. If anyone needs 
it in other branches, let me know.

hello.red segfaults on my ubuntu 12.04 system, any idea?

No, I haven't yet tested the Red codebase on Linux, but I will in 
a few minutes.

So I am the first one to test it on linux? :)

It looks like. ;-)

Cool, it compiles anyway.

Doc, did you know you have a possible theme song? It goes back to 
when I was a young lad but it still rocks:  "Red" by Sammy Hagar. 
http://www.youtube.com/watch?v=sfdy7tC-Us0&feature=fvwrel

Nice Red rock song. :-)

I did this 
$ git clone https://github.com/dockimbel/Red.git

so how come red.r doesn't come down?

I got the redme.md and the license ...

hmm..lots of files don't come down

ooops .. my bad

anyone know how to pull this branch down?

If your `git clone`succeeded, `cd`inside the repo, and do a `git 
checkout origin/v0.3.0`

thanks .. found the answer on SO too

Math operations now supported in Red (integer! values only for now). 
For example:

    a: 123
    a: a + 2
    print a * 6 - a

will correctly output 625.

@szeng: I will look into the Linux issue tomorrow.

I'm awed by the great elegance of it all

The code is very accessible

I like the new macro system, too. I've wanted that for a long time 
(in silence :-)

We'll inform Peter Busser that Red supports round brackets now ;-)

I've updated the recipe in the Syllable build system to add Red:

http://syllable.cvs.sourceforge.net/viewvc/syllable/syllable/system/apps/utils/Builder/packages/Red--current/

On Linux, the executable ends up in the directory of the compiler, 
instead of the working directory

I can confirm the segfault on Linux

Hm, I see Exec in the code :-)

Thanks Kaj, now you can see how all pieces start fitting together. 
Say hello to Peter for me, tell him, I'm sorry we still don't support 
FreeBSD, but I'm looking forward to fix that next time I'll meet 
with him. ;-)

I've found the cause of the linux regression, it was this commit:


https://github.com/dockimbel/Red/commit/fabad833b6bb8b82f9efdf4933c18bfd997a863f

Fixing it...

Doc - looks like you are having fun finally coming with Red :-), 
though it is clear it is a hard work :-)

am I correct that there is no interactive console yet and you need 
to compile source code?

yes, you are correct ...

I would very much like to have a console, but it is not doable at 
this point (unless someone has a bright idea?). We'll add one as 
soon as possible.

Crashes on non-Windows platform fixed (was causing also quick-test 
to fail tests).

# rebol -qw red.r %red/tests/hello.red

-= Red Compiler =- 
Compiling red/tests/hello.red ...

...compilation time: 	 30 ms

Compiling to native code... 

...compilation time: 	 1282 ms
...linking time: 	 	 25 ms
...output file size: 	 	30912 bytes

# ./hello
42

Pekr: I had fun too working on low-level with Red/System, but it 
takes a lot of energy while working at Red level is a lot more relaxing. 
;-)


But this is short holidays, once Red gets mature enough (I bet on 
a couple of months), we'll start working on Red/System v2 (rewritten 
in Red, with a new compiler & linker architecture). This will give 
up the opportunity to reboot Red/System, fix a few design decisions 
if required, extend it, and get a clean and lean new code base in 
Red. I plan to write some architectural specs about the target compiler 
before starting, so all contributors will be able provide me with 
feedback before we implement it. Trust me, you _will_ like the final 
compiler! ;-)

Sure I speak for many who are [silently] watching this and waiting 
for it to mature to the point where we can usefully contribute.

Ashley, same here. I can't really do much right now other than watch 
this wonderful thing unfold.

Ashley: that point is closer than you might think. Even at bootstrapping 
stage, once Red get enough Core features, you and any other reboler 
will be able to add new libraries or port existing one from REBOL 
(should be trivial in most cases). That's not limited to mezz code 
though, you'll be able to add bindings to pretty much anything, protocols, 
provide Red plugins for 3rd-party apps (browsers e.g.), even make 
a View clone if you want (that one could even be a community project). 
:-)

New macros system and Red/System fixes retrofitted from v0.3.0 to 
master branch.

Which branch should we use? 0.3.0. or master again?

I guess master if you want Red/Sytsem, v0.3.0 if you want Red

Exactly.

We'll probably merge all in master by the end of the month and celebrate 
the first Red alpha release.

Master branch is for stable code in maintenance mode, branches are 
for evolutions that could break code compatibility or stability.

Red doesn't work yet for me on Linux. See tracker

Can you apply the non-Windows fix to the Master branch as quick-test 
is failing there now.