World: r4wp

I will have a look today at the reported Curecode issues, then I'll 
get back to Red coding, probably working first on the exception support 
for Red/System (in order to be able to implement EXIT/RETURN support 
for the interpreter).

Thank's for the feedbacks, making a webservice-red-compiler is a 
nice idea, but I made it for lazy people like me to be able to compile 
Red scripts easily. 

Doc: red-lang.org is on a Cheyenne server or a normal hosting service?

Only some static resources are on Cheyenne server, the rest is hosted 
by Blogger (Google).

For false alarms from AV software, please report them to me so I 
can contact AV vendors to whitelist Red binaries.

, how should I report it? What to include? I can prepare zip package 
with those exe files and some info (OS versions, AV versions, etc.)

Just give me the AV software name first, then the source file name 
and compilation optons (if any).

You should also upload first your binary here: https://www.virustotal.com/en/

If the AV software from virustotal doesn't give you the same error, 
you might have an older AV version.

You can post here the link to the virustotal report.

Oh sorry, when I say AV I meant AVira :) Avira Free Antivirus: http://www.avira.com/free-av

Ok I've uploaded to virustotal.com, Detection ratio:	 1 / 46, only 
avira-antivir says "TR/Crypt.XPACK.Gen" virus found.

Here is the link:

https://www.virustotal.com/en/file/2db471babe53dedbd6adf0c5c112976a6692ad000aea83dfa93890f6d1e1b43b/analysis/1365683598/

So you just compiled tests/hello.red or did you use a custom script?

my script is:
Red [ ]
print "hello"

Ok, thanks, will try to reproduce the false alarm and will contact 
AVira for reporting it.

Since it's early days in Red, I'm toying with a lot of ideas and 
revisiting old REBOL funcs as I port them. JS has an interesting 
spin on MAP. I thought I'd see how hard it would be to do in Red.

; JS-like MAP. The order of args to the function is a bit odd, but 
is set

; up that way because we always want at least the value (if your 
func takes

; only one arg), the next most useful arg is the index, as you may 
display

; progress, and the series is there to give you complete control 
and match

; how JS does it. Now, should the series value be passed as the head 
of the
; series, or the current index, using AT?
map-js: func [

 "Evaluates a function for each value(s) in a series and returns the 
 results."
	series [series!]

 fn [function!] "Function to perform on each value; called with value, 
 index, and series args"
	/only "Insert block types as single values"
	/skip "Treat the series as fixed size records"
		size [integer!]
][
	collect [

  repeat i length? series [   ; use FORSKIP if we want to support /SKIP.
			keep/only fn series/:i :i :series ; :size ?
		]
	]
]
;res: map-js [1 2 3 a b c #d #e #f] :form
;res: map-js [1 2 3 a b c #d #e #f] func [v i] [reduce [i v]]
;res: map-js [1 2 3 a b c #d #e #f] func [v i s] [reduce [i v s]]
;res: map-js "Hello World!" func [v i s] [pick s i]

Nice and short implementation! :)

An important note about such code: passing a function! as argument 
is not supported by the compiler yet, so this function could only 
work in the interpreter currently (from console or from a DO block).

Good to know. Thanks. I'm trying to stay just a few steps behind 
you in what I try. :-)

For Red/System fans, here's some new toy: exceptions! Here's a simple 
example for starting:

foo: func [[catch]][
	print "2"
	throw 10
	print "KO"
]

print "1"
foo
print "3"
print ["^/thrown value: " system/thrown lf]

will output:

123
thrown value: 10

A deeper nested example:

foo2: does [
	print "3"
	throw 100
	print "KO"
]

bar: func [[catch]][
	print "2"
	foo2
	print "KO"
]

print "1"
bar
print ["^/thrown value: " system/thrown lf]

will output:

123
thrown value: 100

The implementation is done and I will push it in a few minutes. It 
required about 25 additional LOC to implement all such simple exception 
system (right, 25!). ;-)

So, how does it work? When you need to interrupt the flow of code 
in a function in Red/System, currently you can just use EXIT/RETURN 
to make an early exit. But, sometimes, you need to go up through 
several nested calls, that's where the new THROW function comes handy. 
It will interrupt the execution and go up the call tree to find the 
first function that has the CATCH attribut set. It will then just 
resume execution after the last function call (from which the exception 
has been generated).


If no CATCH attribut is found, it will go up to global code and resume 
from there.

THROW requires an integer! value. Such value represent the exception 
ID and is user-defined. After the resume from a caught exception, 
you can use SYSTEM/THROWN to read the passed exception ID and act 
accordingly (usually using a SWITCH dispatcher).

Important thing to note: system/thrown needs to be manually reset, 
as the last thrown value will stay there if no exception occured. 
Such reset could be done before each call to a function that could 
generate an exception or after processing the thrown value.

I could have added a much more sophisticated system with a true CATCH 
function, but this would have made the implementation way more complex 
and would have taken a lot more time. As I need it only for Red's 
interpreter, I think this way should be enough and will be usable 
by other Red/System programmers to enhance their own code.

Thinking about it, it might be possible to allow an extended catch 
attribut with a integer value to specify the barrier value for catching 
exceptions (and avoid manual re-throwning), something like:

foo: func [[catch 100]][...]


would catch all thrown exceptions with a value <= 100 and let others 
pass up to caller.

What do you think about all this?

BTW, this exception system relies on stack frames unwinding, so it 
won't work for callbacks (CATCH attribut won't be accepted in callback 
functions anyway).

I've considered using a continuation approach for constant-time exception 
throwing (would also work from callbacks), but I didn't find a simple 
enough syntax for defining/using it without having to rely on CPS 
(Continuation-Passing Style) for every functions...

See http://en.wikipedia.org/wiki/Continuation-passing_style

Another note: messing up with the stack (using push/pop) in a user-function 
is fine as long as you returned the stack clean before calling a 
function that could generate an exception. Failure to do so will 
result in a crash. It might be possible to make stack-unwinding for 
exception resistant to such cases, I will investigate that.

Exception handling code pushed. Have fun! ;)

(only IA-32 for now, will add ARM support in the next days)

That sounds great Doc. I collected your comments into a file in %Red/.

Hmm, shouldn't bar print KO in the second example, from your description?

Nope, see first example. This might be a bit non/counter-intuitive, 
I will see if I can improve that.

Ah, I get it now. Yes, that wasn't obvious at first.

I won't be online tomorrow most of the day, will look into that and 
will upgrade the documentation tomorrow night.

So you don't check system/thrown in the func with [catch], correct?

But in the func that *called* the func with [catch].

Right.

I might adjust that tomorrow if possible to make it more intuitive.

Absolutely fabulous Nenad!!!

Good progress. Nice of you to sum it up Gregg, makes the comments 
a whole lot more readable. Filename is a bit awkward though: "esceptions"

Fixed. Thanks Arnold.

I had a Spanish accent last night.

Gregg, I've reconsidered the behavior of the [catch] function attribut, 
if I change it, some use cases become even less intuitive. For example, 
the single function use case (my first example above) performs quite 
intuitively. I think the  vague non-intuitive feeling at the beginning 
comes from our habits with CATCH native in Rebol, after using Red/System's 
way a bit, that feeling just faded away. Anyway, if you have suggestions 
for improvements, it's the right time.