World: r3wp

fix rebol

Right now you can count on LOAD returning REBOL data, or an error. 
This is what makes LOAD trustworthy enough for DO.

seems a significant omission ...

Really? Do you mean #1-773-555-1212 ?

how many times do you see phone numbers like that in real data ?

In REBOL data, plenty. I thought we were talking about LOAD, not 
input processing.

to block is clearly evaluating

Processing UTF-8 to parse REBOL data, yes.

I say UTF-8 because this is R3 LOAD we are talking about - R2's LOAD 
won't change again.

Listen, we had this discussion before and the compromise endied up 
being TRANSCODE/error (added in alpha 39).

Is the r3 group?

this

didn't know that

Yes, I've noticed the same arguments put forward as before.

Oh well, we need a FAQ then !

This discussion pertains to R3, since it is a request for changes 
to REBOL. R2 isn't changing.

I'll do the same thing in another 2 months or so ...  It's a new 
quirk of mine Anton.   ;)  I'll continue to do so until the kids 
on compsci.ca see REBOL as a worthy thing to study, instead of writing 
it off with comments like  "I can't stand the syntax".

That gets really tiresome.

someone will accuse you of trolling

some of us just have short memories!

No Brian, you won't because Carl already made the change in alpha 
39, and is currently writing DECODE.

Even my compromise from the last time you brought this up was rejected. 
TRANSCODE/error and codecs is what we got. Live with it.

I'm doing it with well meaning intent.  I really do struggle trying 
to get young up and coming university students to give REBOL the 
chance I know it deserves.  And sorry Brian, I've haven't tried A39 
yet.  I'm still running the A33 for Linux.

Well, I already rewrote LOAD to take advantage of the TRANSCODE changes. 
It should go in the next build.

This includes LOAD/next, btw.

Like LOAD/header, it is better than R2 :)

This is very cool news ... I'll crank up wine again on an a40.exe 
to see ... time to catch up with recent developments again.

I think upgrade works with the Linux version now, and there are Linux 
builds on the releases page.

Even cooler news from the upcoming LOAD:
>> load ["print 'hello" "print 'there"]
== [[print 'hello] [print 'there]]
Works with files and urls too - Carl's idea :)

uh ?

I've been trying upgrade ... just did a minute ago ... it stashed 
an r3-a40.exe  so I wouldn't have bothered to look ... but am now 
as you made me all keen and curious.   And yes, the releases page 
has updates I didn't notice.

Thanks Brian

LOAD of a block will treat the block as a collection of things to 
load, so it will load all of them The code is this:
    map x source [apply :load [:x header next all unbound]]

Yeah, the upgrade returns anLinux binary with a Windows name :)

an -> a

ahah i was about to said it was a shortcot for
map str ["print 'here" "print 'here"][load str]

to slow

Yup, except with APPLY so the refinements can be propagated.

MAP and APPLY are native in R3, as fast as FOREACH and function calls, 
respectively.

map is currently underated, it's a really cool function

Even as mezzanines they would be useful, so MAP and APPLY are part 
of R2-Forward as well.

I use them in R2 every day :)

Well, APPLY more often than MAP, but still.

I still don't see the performance hit of a lexical scanner that defaulted 
to 

make foreign!"" - One word, backtracking. It needs MAGIC to do what 
you want. MAGIC is expensive.

Furthermore, I don't believe that this would attract even one more 
user to REBOL.

Well put :)

To be honest, i can see his point.

If instead of failing on the first error encountered, we could have 
a load-foreign which accept a user call back function, each time 
an error occurs.

Then, we could do some  handy conversions meanwhile the loading process.
Don't say it would be a useless thing guys.

it's easy to simulate with transcode and parse but we need speed 
here

Failure is your friend. If it doesn't fail on errors, you can't trust 
the output and yo have to do the error checking in your code.

i'm not talking about the standard behavior of LOAD here