World: r4wp

Fortunately, I can skip the Windows discussion :-)

Actually, my last issue in on non-Windows systems, with the run from 
"console vs shell". Hard to fix one without breaking the other...

With the help of Andreas and Peter, we've fixed the last remaining 
non-passing cases. I will merge the fixes in the master branch tonight, 
in the meantime, if you notice any regression or issue with paths 
handling, please report them here before the merge.

It's great to hear you're making continuted progress!

Thanks Nick.

Just donated 50 EUR so that Red project does not feel bad by my move 
to donate also to R3/Android/GUI :-)

Thanks Petr! :-)

I've done a full build run with the path fixes, without regressions

Merged branch `fix-issue-277`. Thanks to all contributors and testers 
for helping clean up those issues.

http://www.rebol.com/cgi-bin/blog.r?view=0527#comments


Fork: "I am porting Red to R3--and while I won't claim I'm "almost 
done", I will say I've made significant progress. Red/System now 
builds a working hello.reds under both R3 and R2."


Great! Like Nick says, hard to keep track of everything happening 
these days. :-)

surprised by Fork even looking into Red, he seemed to be interested 
mainly in R3 itself ...

Well, in fact I don't understand, what he actually did. What I would 
expect is someone writing R3 in R/S, so that it would got all backends 
R/S supports?

It sounds like he ported the Red compiler, which currently runs on 
R2, AFAIK?

He ported the Red/System compiler from R2 to R3 and he seems to be 
working to port Red compiler from R2 to R3 too.

Kaj should be pleased :-)

pity he did not start porting Red/System into Red, that would speed-up 
removal of dependency on Rebol :-)

Why don't we wait until more of Red exists? Or is Red feature-complete 
for core language features that would be used to write a compiler? 
If not, and you ported the Red compiler to the Red subset you have 
now, it would be a lot of work to do. And you'd want to rewrite it 
when you actually implemented the Red features you would want to 
eventually use in the compiler. Removing the dependency on Rebol 
should be done eventually, but it isn't as high a priority as implementing 
Red, right?

Doc's plan is to implement the whole stack using Red rather sonner 
than later.

AFAIU, the priority has always been to implement as much of Red as 
is needed for bootstrapping.

Cool. We can wait to do the bootstrapping until that is done.

Does #192 apply to SWITCH and CASE, too?

Very possible, it should affect every Red/System statement used in 
expressions. I don't think this is fixable before Red/System v2.

I haven't been of much help to you yet. I even may have been "too 
loud" sometimes polluting this discussion with my preferences. What 
I want to say now, though, is that I consider it good to have more 
dialects of Rebol instead of having just a totally compatible copy, 
so, please, take that as an encouragement and appraisal of your work.

Thank you for your kind words Ladislav.

Doc, would you update this page of yours http://www.red-lang.org/p/documentation.html


to indicate that Red chat is occuring at http://chat.stackoverflow.com/rooms/291/rebol-and-red

The Rde presentation shows the use of the binary Red. In it shows 
how to compile to get a cgi and a dynamic library. Are these also 
implemented in the current compile scripts? In that case that holds 
a good argument to update the Redcompiler.r script. It needs some 
work anyhow I noticed, it is rather location dependent atm.

Rde=Red

Arnold: no, it's not implemented yet, it's a target.

GrahamC: I will add to the Red web site only links to strictly Red-related 
communication channels. OTOH, I can tweet this link.

I'd like to know if it would be possible to use Red/System to implement 
a program to capture frames from a web cam on a Raspberry Pi?  Or 
would this be better performed in another language?

I know that François Jouen is already using Red/System to make image 
capturing from multiple cameras on OS X. Also as a rule of thumb, 
everything that is doable in C can be also achieved in Red/System.

That it is a target I can see now I have viewed the presentation 
a second time. Do you have a faint idea of a timeline when various 
stages of Red could become part of the real world? So version 4 in 
april and the first binary Red in 2015?

Binary Red could be added in a few weeks (except for the interpreter 
with console which would need an additiion binary), we just need 
to encap all Red codebase files in one executable.

For a complete single binary, we need Red to be self-hosted, so probably 
not before end of 2013.

additiion
 = additional

The interpreter console is already a binary

Thanks for the info.  I have a 512MB RasPi and a 16GB SD card on 
my desk right now.  I'm going to give it a shot soon.

Can I pass function pointer as an argument to another function in 
Red/System?

Yes

However, it's not yet supported for functions defined by #import, 
so if you need that, you have to write a wrapper function

Also, in some places you have to cast the function pointer to an 
integer to pass it

Ok, thanks. I unfortunatelly hadn't chance to check Red/System in 
last few months. I'm very glad it can be done, I have to find some 
time for Red/System again.

Since Red needed jump tables, you can also go the other way around, 
and cast an integer/pointer to a function, then call it

Here's the code for the Red GUI IDE:

Red []

#include %GTK/GTK.red

view/title [
	text: area
	button "Do" [
		unless any [
			none? script: get-area-text text
			empty? script
			empty? code: load script
			unset? result: do code
		][
			prin "== "
			probe result
		]
	]
	button "View" [
		all [
			script: get-area-text text
			not empty? script
			not empty? code: load script
			view code
		]
	]
	button "Quit" close
] "Red GTK+ IDE"

Nice! It's amazing how fast you came up with a VID-like dialect for 
Red.

Well, most of the work is in the Red/System layer that I did more 
than a year ago

Same for the other bindings

Plus, when putting a Red layer on top of it, you're staying within 
Red and Red/System, so you're on known terrain. Starting a new binding 
in Red/System throws you into the abyss of the external library's 
C code, headers and idiosyncracies, and documentation that may or 
may not exist or be correct

What can you do for Android where this is no gtk?