World: r3wp

Working on locate.r;  saving a database after a scan of the library 
scripts can't be reloaded
autoextract.r has the following inside it:
    output: [{Self-extracting REBOL-compressed file
        REBOL [
            Title:  "Self-extracting compressed file"
            Date:  } now {
            File:  } mold infile {
            Author:  "Autoextract function by Bohdan Lechnowsky"
            Comment:  ^{
               Simply run this script and it will 
               decompress and save the file for you
            ^}
        ]

        if exists? } mold infile { [
            print ["} infile { already exists, please rename"
                           " existing file and run again."]
            halt
        ]
        write } mold infile { decompress 64#} mold file
    ]
    write outfile to-string reduce output


How do I get REBOL to keep the ^{ and ^}  across a save/all and load? 
  locate.r keeps a reference to all block! info for the tour sequence. 
 LOADing this (after a SAVE/ALL) causes an invalid string error. 
 Any hints?

Oh, and the code is passed thru the pretty-print parser (to build 
up the references) before the save/all

one of my pet peeves is that to-block craps out if it encounters 
an unknown datatype

why can't there be an option to turn illegal datatypes into strings 
...

I'm using to-block so that I can use block parsing of course

Yeah, me too ... always.   But R3 TRANSCODE can trap that now ... 
umm, I just don't get the whole LOAD/NEXT thingy in context of parsing 
over block! and paren!   Gabriele has posted links, just never dug 
in.

>> to-block "23 May, 2008"
** Syntax Error: Invalid word -- May,
** Near: (line 1) 23 May, 2008

Ok, now why is "," in particular not allowed in a word?

Has anyone ever detailed the voodoo of caret escapes in strings?


^^^{   does not return ^{  as I read it should.  It's ==ing as ^^{, 
but I'm not sure if this a post process of the == result display. 
 ??  Seems like voodoo.  And instead of exploring, I'd rather just 
read something this time.

Having nothing intelligent to add - to me the comma is a little voodoo 
too; I'll just ditto your sentiment.

which function allows me to traverse a series and remove at the same 
time?

remove-each

Or while?

cool

how's this 

>> date: "* 10 May, 2008"
== "* 10 May, 2008"
>> d: parse date none
== ["*" "10" "May" "2008"]
>> remove-each b d [ not any [ parse b alphas parse b digits ] ]
== ["10" "May" "2008"]
>> d: to-block form d
== [10 May 2008]

I'm trying to clean up OCR'd text prior to parsing

to end up only with integers and alphas ... is this bullet proof?

>> to-block "3a"
** Syntax Error: Invalid integer -- 3a

Not entirely...

it won't pass my parse rule

I parse digits and chars separately .. I'm not using an alphanumeric 
parse

ok, if that's the case, you should be fine.

Yeah I'm playing too ...

I'm sure the parse gurus can do this all in one parse rule!

I wanna junk! datatype ... parsed (made / loaded) up to next space 
during interpret.  Then we could read scripts modified by normal 
people.  Might be a lot of junk! but I'd rather write a junk! handler 
than try and trick REBOL.

read = load

yeah ... that would be neat.

I'd call it crap! though

date: "* 10 May, 2008"
allowed: union union alpha digit charset " "
parse remove-each char date [not find allowed char] none
== ["10" "May" "2008"]

but you got a problem with this
date: "10 May,2008"  ---> ["10" "May2008"]

date: "10 May,2008"
parse replace/all date complement allowed " "
= ["10" "May" "2008"]

date: "* 10 May, 2008"
parse replace/all date complement allowed " "
== ["10" "May" "2008"]

which passes a charset to to REPLACE.

>> a: [(i)]
== [(i)]
>> repeat i 5 [print i compose a]
1
** Script Error: i has no value
** Where: halt-view
** Near: i

>> repeat i 5 [print i compose load mold/all a]
1
** Script Error: i has no value
** Where: halt-view
** Near: i


Is that correct? I'm obviously missing something, but I don't know 
what. Does COMPOSE not work inside the REPEAT context?

>> b: ['i]
== ['i]
>> repeat i 5 [print i reduce b]
1
2
3
4
5
== [i]

This works as expected.

solved it:

>> a: [(i)]
>> repeat i 5 [print i compose bind a 'i]
1
2
3
4
5
== [5]


I assumed that LOAD MOLD/ALL would kill the existing bindings and 
re-bind it to whatever context it was being run in. I guess it doesn't 
do that.

I think LOAD just binds to global context.

yes, I think it does.

:-/ Yeah, that must be the answer. Do we need a /local (or something) 
refinement for LOAD?

c: context [print: "local" w: load "print"]
type? get c/w  ; == native!

Geomol, why add another refinement when you can just use BIND, which 
allows you to bind it anywhere ?

Yes, LOAD is native. !? What's the point?

Anton, right. Good point.

And in any case, what does "local" mean ? How would LOAD determine 
what is meant by local ? The block it's in does not have any associated 
context.

Ah, let me reconsider the native! thing. Was thinking in terms of 
blocks. It's an object! of course. ...

Only the words in the block know what context they're bound to.

>> probe get a/w
native

Heh! :-) I'm not so sharp today.

In the code above, I make an object which has a local word 'print 
(with a local value "local"), and another word 'w whose value is 
LOADed from the string "print" (which becomes the word 'print). This 
new word is bound to the global context. Where else could it be bound 
? The word 'load in the block above is not bound to the context I 
made, it retains its global binding (which is why it actually does 
what we expect it to).

I was doing this:
a: context [w: load "print"]
get a/w


Same thing. I understand you now, Anton. The words know, what context 
they're bound to. So it should all just be sorted out with BIND. 
And BIND can be confusing (at leat I find it confusing now and then).

Yes, the "invisible links" of bind can be confusing.

Thanks for the explanation! :-)

np