World: r4wp

In many ways, R3's module system design is even more beneficial for 
a language like Red than it is for R3 itself. Actually, that was 
one of the things I was taking into account when we were thinking 
it through. Back before Red was announced I was thinking about putting 
a JIT compiler into R3, and R3's extensions are similar in some ways 
to what modules would be in a Red-like language. So R3's module system 
was basically designed with Red in mind.

In order for R3 to get the full benefit of its module system, Ladislav's 
include and Saphiron's encapper would have to be enhanced to use 
and process them. Red can get the benefit from day one just because 
it's compiled.

red>> {}
*** Load Error: string ending delimiter } not found!
== {}}

Error fixed.

About the path composition for files, I might give it a try tomorrow.

red>> ""
*** Load Error: string ending delimiter not found!
== """

Sounds like we really need LOAD regression tests if we want to finish 
this...

Yep. Another one:

red>> view [{}]
Box: skipping unknown dialect word "{".
Box: skipping unknown dialect word "}".

It's on my todo list to do more LOAD tests for R3. You can use those 
then, at least as a start.

Unfortunately they won't happen today.

I need to port them to Quick-Test anyway.

BTW, I have no clue where the R3 tests are located online?

https://github.com/rebolsource/rebol-test

Thanks.

file! is suddenly broken:

red>> print %x
unset

Those tests manage to be unified between R2 and R3 by tagging the 
ones that aren't. A #red tag could be added...

Works here.

Where do I find LOAD tests? There are only these ones: https://github.com/rebolsource/rebol-test/blob/master/load-tests.txt

Fresh build, on Linux

Let me stash my changes to see if there's a side-effect.

There aren't that many yet, which is why I need to add some.

All tests are here: https://github.com/rebolsource/rebol-test/blob/master/core-tests.r

Wait, my console-pro isn't rebuilt

Fresh console build with latest pushed commit (on Win7):

red>> print %x
x

I'm getting #411 again on two programs

With the exact same error message?

Yes. I've checked in my current state of GTK so you can test it

If you update everything, it happens on console-pro and GTK-IDE

{} is OK now that I've forced a build

On Linux only?

Dunno, probably not

I'm running View 2.7.8.4.3

Can you try it with /Core 2.7.6? (just in case...)

Sigh. rebol.com only lists 2.5

Found it in the maze. It works

Great!

Well, I haven't used that in many years. I would like it to work 
with 2.7.8

Have you tested with Core 2.7.8?

I only trust 2.7.6 for my production code, I had too many weird behaviors 
and bugs in 2.7.8. 2.7.6 has some bugs too, but at least I can spot 
them easily and it seems to much more stable overall than 2.7.8.

Same issue

2.7.6 and 2.7.7 have problems, especially in View, that make them 
unstable on Linux. I'm using 2.7.8 in Syllable

2.7.7 is definitely a no-go.

It works fairly well for me

Red works OK on those versions, except this problem

I have never tested deeply View on non-Windows platforms, as I never 
needed it for my production code.

I will give it a look tomorrow testing with 2.7.8.

Thanks

Make sure not to change anything, as any shift in the code makes 
the problem go in hiding