World: r4wp

Oh, I see, you were going to implement VALUE? for validation. I just 
didn't think you meant checking the entire input; I thought you were 
talking about the result

I meant the whole user input, mainly for catching undefined words/paths 
and hanlding the error out of DO.

Maybe I will do it myself in the console script...

Thinking about it, that would reject any user code that uses words 
as symbols, wouldn't it?

I have a loop written that does the evaluation, even without VALUE? 
but it doesn't seem like a good idea to me

red>> x: load "view button" forall x [print unset? get x/1]      
     
false
true

Undefined single words were never a problem in the interpreter before. 
That's why I could write Redpages with a header:

Red []

They were simply ignored. After I requested the warning message, 
the Red word produces such a warning, so for now I write:

'Red []

By the way, are get-paths supposed to work?

Nope, not yet.

DO doesn't support a Red header yet.

You should strip it from a LOADed block before passing it to DO.

I know, but it worked

I need to fix some interpreter issues revealed by Peter's port of 
~2500 tests to the interpreter. There's about a dozen failing tests 
to fix.

Once that done, I will have a look again at those error reporting 
issues.

I agree that it is not yet possible to deeply validate user input. 
I'll see if I can find a cheap workaround for the release.

OK, thanks

7 failing tests to go until complete equivalence between Red compiler 
and interpreter. :-)

nice progress

Great!

Nice!

I'm getting a weird crash if I load the following in the GTK-browser:

function [] [
	[text]
]

bash-4.0# ./GTK-browser test.red 

*** Runtime Error 1: access violation
*** at: 08063687h

It doesn't happen if I load it in the console

This fixes it:

function [] [
	text: ""
	[text]
]

But this doesn't:

function [] [
	text: none
	[text]
]

Actually, it crashes by just loading:

none

Sorry, strike that last one

I've put it in the tracker

Great stuff guys,  been taking a bit more time to get to know RED. 
 Great work Doc, Kaj, Peter, and the rest of the testers and submitters.

Thanks, glad you like it :-)

I do.  Good work!

The upcoming release will be quite recommendable, both the compiler 
and the interpreter. Until now, only Red/System was ready for real 
use

Yes, I'm more exited about Red these days then REBOL open source.

Thank you Paul! As you've seen, we are working hard to make our dreams 
come true. :-)

:-)

Phone company in Holland has launched new mobile service. "All you 
need is Red".
http://www.vodafone.nl/Red

I can't agree more. ;-)

Interesting, they also copied our 3-layer tower concept...;-)

I've found out an annoying bug in the way the interpreter sets the 
stacks layout for function/native calls with refinements presented 
in arbitrary order, it results in assigning the wrong arguments to 
refinements in some cases (caught by 3 unit tests only). I've worked 
most of the day on changing the way function/native calls are handled 
by the  interpreter to get it right in all cases this time. I hope 
to finish it for tomorrow.

The right and efficient handling of refinements is really one of 
the most difficult parts in making a Rebol language interpreter/compiler.

Keep good notes, so you can write designer's notes for future implementors. 
:-)

I'm not sure yet what the optimal way would be for runtime refinements 
evaluation, I've used a bitfield-based caching method in R-sharp 
to pay the full cost on first evaluation only. I'll try to implement 
a similar method for Red interpreter later. For the Red compiler, 
the cost is paid once only during compilation, there is no specific 
runtime overhead.

I could write a book about designing and implementing a Rebol-like 
language, counting R#, I've implemented two interpreters and one 
compiler. I've also implemented a partial Rebol in Rebol interpreter 
five years ago (never published), mainly aiming at providing step-by-step 
and stop/restart evaluation features for debugging purposes. But 
my first tests showed that it  was running about 50 times slower 
than R2 itself, so unusable for real code.