World: r3wp

I didn't know you could use find with a charset

>> b: complement charset "|"
== make bitset! #{
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
}
>> next find/reverse tail "abc|||" b
== "|||"
>> head clear next find/reverse tail "abc|||" b
== "abc"

FIND/reverse/tail doesn't work in R2.

I'll give it a go... ta

So you might need to do a bit of tweaking for the R2 version, but 
it's a start.

is this being backported to R2?

FIND/reverse/tail works in R2, but not with charsets. It's a bug.

as I thought ... no find with charsets

oh ... ooops

FIND works with charsets in R2, but the /tail option doesn't. It's 
a newly discovered (just now) bug.

just now ??

Yeah. By me, just now, while I was doing this experiment.

neat

Thanks :)

find/reverse tail a b only finds the first |

>> a
== "abcd|as|dsf|||||"

>> index? find/reverse tail a b
== 16

oops ...

no sleep :(

That's where the CLEAR comes in :)

By George I think I've got it!

BTW, I think trim/with/tail should actually do this .. but trim/with 
removes characters inside the string.

Yeah, for TRIM /with implies /all.

replace/all does the same ... so perhaps trim/with should be changed

>> map-each a [] [1]
** Throw Error: Return or exit not in function
** Where: map-each
** Near: return any [output make block! 0]

>> system/version
== 2.7.8.4.2

Darn, my bad. It's the [throw] function attribute. Don't worry, there's 
a way to reorganize the code so no RETURN is necessary.

Thanks for the report. I'll fix it in R2/Forward right away.

Here's a working version:

map-each: func [

 "Evaluates a block for each value(s) in a series and returns them 
 as a block."
	[throw catch]

 'word [word! block!] "Word or block of words to set each time (local)"
	data [block!] "The series to traverse"
	body [block!] "Block to evaluate each time"
	/into "Collect into a given series, rather than a new block"

 output [any-block! any-string!] "The series to output to" ; Not image!
	/local init len x
][
	; Shortcut return for empty data
	either empty? data [any [output make block! 0]] [
		; BIND/copy word and body
		word: either block? word [
			if empty? word [throw make error! [script invalid-arg []]]

   copy/deep word  ; /deep because word is rebound before errors checked
		] [reduce [word]]
		word: use word reduce [word]
		body: bind/copy body first word
		; Build init code
		init: none
		parse word [any [word! | x: set-word! (
			unless init [init: make block! 4]
			; Add [x: at data index] to init, and remove from word
			insert insert insert tail init first x [at data] index? x
			remove x
		) :x | x: skip (

   throw make error! reduce ['script 'expect-set [word! set-word!] type? 
   first x]
		)]]
		len: length? word ; Can be zero now (for advanced code tricks)
		; Create the output series if not specified
		unless into [output: make block! divide length? data max 1 len]
		; Process the data (which is not empty at this point)

  until [ ; Note: output: insert/only output needed for list! output
			set word data  do init

   unless unset? set/any 'x do body [output: insert/only output :x]
			tail? data: skip data len
		]
		; Return the output and clean up memory references
		also either into [output] [head output] (
			set [word data body output init x] none
		)
	]
]

I'm studying the RIP archive format and am wondering:


Why does LOAD allow binary "junk" at the end of a file, if it has 
a REBOL [] header, while it does not, when the header is omitted?

I don't think that LOAD allow binary "junk"

afair, LOAD allows REBOL scripts to be embedded in "junk"

No.. it doesn't... it's possible to DO a script which has some sort 
of junk, but not LOAD.

>> load {234523$%$%^& rebol [] print 1}
** Syntax Error: Invalid integer -- 234523$%$%&
** Near: (line 1) 234523$%$%& rebol [] print 1
>> do {234523$%$%^& rebol [] print 1}
** Syntax Error: Invalid integer -- 234523$%$%&
** Near: (line 1) 234523$%$%& rebol [] print 1
>> write/binary %x.r {234523$%$%^& rebol [] print 1}
>> do %x.r
** Syntax Error: Script is missing a REBOL header
** Near: do %x.r
>> write/binary %x.r {234523$%$%^& ^/rebol [] print 1}
>> do %x.r
1

you can have junk at the beggining as long as you have the header 
there (  rebol at the newline start)

rebol with following block.. this does not works:
>> write/binary %x.r {234523$%$%^& ^/rebol none print 1}
>> do %x.r
** Syntax Error: Script is missing a REBOL header
** Near: do %x.r

this works as well:
>> write/binary %x.r {[^/rebol [] print 1] 34532$%*&%$#}
>> do %x.r
1

hmm.. ok... the LOAD is possible as well:
>> load %x.r
== [print 1
]

so you are right

I guess it's how the load/next is implemented... if the header is 
inside a block, it stops there.

I forget: How do you open an Explorer window from Rebol?

If you want a file requester: request-file, if you just want to spawn 
a new Explorer window for the user, this should work: call "explorer".

do you know if the call method works under win7?

Works, tested on Win7 with 2.7.6 & 2.7.8.

thanks very much

You're welcome.

Is there a trick / limit to just how deep one can create an object 
which itself has nested objects stored in a block? I have this xml 
string that I converted to a block via parse-xml but at about two 
levels in, it remains a block (make object!...)

Are you missing a reduce?

Or try Gavin's code:
   http://www.rebol.org/view-script.r?script=xml-object.r

I'm using this one http://www.rebol.org/view-script.r?script=xml-parse.r

(not an object)

Yes, I am using xml-parse and then xml-object. My question is something 
that I have dealing with for a long time actually. So is there a 
limit to how far something is reduced in terms of nesting?