World: r4wp

Pekr: %rsc.r, like it or not, the naming scheme was following the 
usual conventions for naming compiler launchers, maybe you would 
have preferred %red-system-compiler.r?

I would prefer it would not exist. I find "do/args %rsc.r "-v 5 %tests/hello.reds"" 
still being rather cryptic and I hope everything gets replaced, once 
we get red.exe?

Parallella: Red should be able to run on it from day one as we already 
support their system (Ubuntu/ARM). For the risc chips cluster (Epiphany), 
simply making a Red/System backend for them would not be enough to 
leverage the computing power. We would probably need some new abstractions 
at Red level, specific new natives in Red or even dialects to take 
real avantage of it. For example, we could have a MapReduce native 
support in Red that would   delegate execution to such kind of cluster 
(there are other competing hardware products in that area).

Pekr: you understand that building Red is not going from 0.0 to 1.0 
in one step? So, like in any other long ang complex building processes, 
you have intermediary building steps and states that are not necessarily 
representative of the final product. Think of a house in construction 
with scaffoldings, you don't point at the scaffoldings saying that 
the house will look horrible.

I've found a nice keyboard configuration that seems to do everything 
I want

Petr, there's already a red.exe in my downloads; just not a compiler, 
but the interpreter :-)

rsc.r works better now

I would still like the default output to be deposited in the working 
directory, instead of the builds directory

Pekr: You are welcome to use Online Red & Red/System compiler here: 
http://bircomteknoloji.com:8181/

Just don't forget to change script header when you switch between 
Red & Red/System. 


Red compilation takes 10-25 seconds, Red/System compilation is 1-2 
seconds.

Endo: did you encapped Red compiler?

@Kaj, The Yen sign has disappeared here! Congratulations! :)

I would still like the default output to be deposited in the working 
directory, instead of the builds directory

 I think I agree with this. In the ideal situation you could specify 
 these things, maybe in a settings file or in a preference in a compilation 
 assisting program. (Started one once)  

The integration of rsc.r within red.r sounds as a logical step. (rsc.r 
Red System Compilation, not so bad and a clear difference from red.r 
for Red scripts)

@PeterWood Thank you again Peter! 

Peter answered a question on the Red mailing list (all subscribe!) 
about me calling a function in Red like f(10) where it should have 
been f 10 and I didnot get this. The (10) part was being processed 
as a paren! type so the value was calculated before giving to the 
function f as input.

Time is almost ripe for Red school group.

DocKimbel: Parallella: Sounds like a very interesting challenge. 
:-)

They have devs focussing on Erlang, Go, interesting stuff. Beating 
them with Red is ambitious. Pointing them to Red is ok.

Doc: "did you encapped Red compiler?" Nope, RedCompiler.exe is just 
calling the rsc.r or red.r according to the extension of given script 
file. It should be placed in the red-master directory.

I tried to make a encapped Red compiler but there are some problems 
with #include or other compiler directives.

Once we merge %red.r and %rsc.r, I will look into encapping the whole 
thing, so we'll be able to start distributing Red as a unique binary 
file.

Yeah it will be great. People can try Red & R/S easily then.

ZLib binding for Red/System released by Bruno:

https://github.com/dockimbel/Red/tree/master/red-system/library/zlib

Looking at http://www.red-lang.org/p/contributions.htmlit seems 
to me, that Red has more bindings, than for R2 + R3 combined :-) 
Maybe just an impression, as I miss such a conscise list on rebol.com 
website ....

That page is incomplete...

Am I doing something wrong with this?:
Red/System []
mem: declare pointer! [byte!] len: 10
while [all [0 < len: len - 1]][mem: mem + 1]


*** Compiler Internal Error: Script Error : get-function-spec expected 
name argument o
f type: word
*** Where: get-type
*** Near:  [either 'op = second get-function-spec]

What are you filling mem with?

I am not filling mem, that is only an extract of my code (a part 
of a search function).

Why the compiler gives an error?

Could be it is a compiler error, the message suggests it imho.

Pointers are not my specialty :(

Have you previously done a while loop in Red/System like that? Try 
it a little simpler while [0 < len][mem: mem + 1 len: len - 1] to 
be sure it is not the combined statement that is confusing the compiler. 
(Just trying to help here until the real experts jump in)

It seems the all [] inside the while test block the problem, so how 
can I do more then one test inside it?

Assignments can't be embedded, so you have to split them out into 
a separate expression

put all [] in a block too?

len: len - 1  len > 0

keep it simple

The ALL [ ] is not needed

Good thing Red isn't called Green (as in combined blue and yellow)

The all [] was meant to be a test to see if Red/System can handle 
it?

It can, but it's not needed here

yep

Not needed here but the original was:
while [all [mem/1 <> string/1 0 < len: len - 1]][mem: mem + 1]

while [len: len - 1  len > 0]

so try

while [all [mem/1 <> string/1 len: len - 1 0 < len]][mem: mem + 1]

while [len: len - 1  all [mem/1 <> string/1  len > 0]]

6 seconds, you are fast Kaj!

It has taken 45 years for someone to say that to me :-)

Ok, understood.

I would like to have that feature in Red/System v2 :-)

Poor Marco! Hope this is still helpful!
I think those 'features' are confusing (and bad practice)

Even while [len: len - 1 0 < len] or while [0 < len len: len - 1] 
is terrible if you ask me. Luckily you do not ask me. :)

You mean the features that define REBOL?

while [0 < len len: len - 1] doesn't work, either in Red/System or 
in REBOL

I mean code like 0 < len: len - 1 is confusing to me.