World: r3wp

oh my... it could be simple, just load as junk! until you found a 
valid separator (blank, newline or tab) then continue to load.
What's the problem ????

Those who are saying endless that it's better to throw an error have 
never been in that case...

And if it can not be included in core as a new datatype! (constructed 
by to block!) then it's useless. I don't want it as a mezzanine because 
it would be slow.

at least junked tokens could be formated as a string! it would be 
more usefull than thorwing an error and stoping

to block! could return a false status if there are junks but we don't 
want useless errors anymore...

Doc, the point to LOAD/else is that it requires a parameter that 
is the answer to the question of what the calling code wants to happen 
at that point. This solves your concern, and is the major difference 
relative to all of the foreign! proposals.,

I don't know whether /else is the right name for that option, but 
at least it's short.

Load/foreign ?

More like load/on-error.

It would require you to provide a handler, or perhaps a word that 
denotes a stock handling strategy.

Like load/on-error "10,000,000.00" 'string.

Or 'skip.

by defaut it  should be a string conversion with a charset or a string 
with delimiters

By default, it will be an error. The default will be when the /on-error 
option is not used.

Otherwise you will be *required* to specify a strategy for dealing 
with the data, perhaps as a function or code block if you like.

you know what i mean, i'm talking about a default conversion when 
the option is selected

There will be no default - the parameter will be required.

It's either specify the option or don't.

like for parse.
default use: parse data none
with specific separators: parse date "..."

You are passing a parameter there - it's not the same thing. If we 
allow a none parameter (which we shouldn't), it should mean 'skip.

However, there should be a 'local parameter for localized numbers 
and dates.

we don't need to skeep, the only skiped chararcters are the separators

*skip

Yeah, you should definitely skip separators. Use load/on-error data 
'skip if you are expecting separators, as REBOL doesn't have them.

Except for whitespace, of course.

see the sqlab code, it's exactly how it should behave

his load-all, we don't need more fonctionnalities

No, that won't work. It will break on nested structures.

The whole point oif LOAD is handling the whole data syntax of REBOL.

oif -> of

i  talking about the functionnalities not about his implementation

So am I. That functionality won't work, for reasons Doc most recently 
explained.

we just need a list of separators when a wrong loadable value is 
encountered to continue the loading

reasons Doc exposed are false

We have a list of separators: Whitespace. Anything else requires 
special handling that will need to be specified. The only problem 
with Doc's comment is not getting that part of the LOAD/else proposal.

anyway if your objective is to build a mezzanine it's useless, it 
will be slow, i will continue with my own pre-parsing process

LOAD is a mezzanine, but it calls natives. My goal is to make LOAD 
useful.

Please contine to do your preparsing. I was doing this on btiffin's 
suggestion, and he seems to be afraid of PARSE :)

Umm, yes and no on the fear.  Yes fear kept me from holding a lecture 
on the subject, but I usually PARSE from reading the pretty print 
code.  That's how my locate utility works.  But I'm not concerned 
with us.  I'm concerned with construction bosses and non-tech professors 
having access to a programming language and learning maybe one or 
two tricks a week.  I'm also on the side of the gurus in terms of 
correctness and concise coding, but I'd like to see REBOL ,the system, 
that out of the box would be a robust battle tank.


Add taint to the fuel, it would still function; perhaps not gracefully, 
but the big guns would still fire.  Today, the slighest spoonful 
of sugar and our tank dies on the field, no movement, no guns.


foreign! and Steeve's suggestion of scan till whitespace (and yes, 
some source code would load as almost all completely foreign! gibberish 
if a quote was out of place, but so, we can take that and fix it). 
 But at least REBOL wouldn't die; the data/code would be loaded and 
inspectable.  And yes, this could lead to the odd rare catastrophic 
failure, but we get that potential with "clean" datatype! scripts 
too.  I think the slight increased risk is worth the new group of 
users this could attract.

Sorry if I misrepresented your position Brian, I was trying to be 
humorous. I've just put in a request to tweak TRANSCODE's handling 
of commas. If that request goes through, I will be able to add the 
/else option to LOAD. With a few more tweaks I can increase the speed, 
make more of the process native, etc. This is not preventing REBOL 
from dying - it is just allowing you to provide a defibrillator :)

In case you wondered about the origin of CTRL-ALT-DELETE - this is 
actually kinda funny http://www.flixxy.com/computer-history-ctrl-alt-del.htm

There will be everywhere soon - the revolution of the TIRE http://www.flixxy.com/car-tire-technology.htm

Oh Brian.   I take few thingsseriously ... well, except my belief 
systems.  ;)   Me too, I forgot the smiley after ... pretty print 
code.


And Yayy.   Now if this can be out-of-the-box REBOL for linguistic 
profs and science types  ... woohoo!

btiffin - did you read R3 'transcode description? It seems to have 
relaxed execution, returning error as an arror. Not sure it would 
be what you want, but maybe? http://www.rebol.net/wiki/Transcode

Actually, that is exactly what we need. One problem though:

>> transcode "a,"
== [make error! [
        code: 200
        type: 'Syntax
        id: 'invalid
        arg1: "word"
        arg2: "a,"
        arg3: none
        near: "(line 1) a,"
        where: [transcode]
    ] ""]

I've requested that this be changed to:
>> transcode "a ,"
== [a ","]

putting off the error until the next call. That change would be enough 
to do LOAD/else.

All it would require is to make "," a delimiter in the scanner - 
a trivial change for Carl.

Sorry, two messages back: "a ," -> "a,"

in the second example.

Pekr;  I think a convo we had on the blog wayy back was partly why 
Carl relaxed TRANSCODE  ;)

We went through a phase of trying to name the junk! datatype, and 
very real issues were raised about where the lexical scan should 
restart after.  Then someone discussed the linguistic analytic potential 
and another very real concern about polluting the semantics of REBOL 
datatypes was raised.  Carl may have been afraid we'd all run off 
and produce "any old crap that works", where I aim to provide a console 
that takes "any old crap" and works.  ;)  Leaving Gabriele and others 
free to use the ever cool true semantic meaning of data and code 
and leave junk! that floats for analysis of real world information 
sans REBOLification.


Part of that conversation lead to and is included in http://www.rebol.net/cgi-bin/r3blog.r?view=0078#comments

BrianH: ... then I expect you will propose the change to Carl, to 
enable load/else? :-)

any known rebol datatype should be recognised, and the rest should 
be assigned under junk! or similiarly named datatype. What is AI 
about that?

 Telling the different between a REBOL value and "the rest" is AI. 
 If you can without AI, then "the rest" is defined with a specific 
 parse rule... then you can just use string parsing, and it's not 
 a human language anymore but a specific language you just designed.