World: r3wp

*usually

This one?

http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=prolog.r

not this one

but the same goal

do you remember the author ?

no sorry

i'ts verry old

rebol.org was not created yet

i mean

But you were not around at this time, were you ?

i was

i'm using Rebol since 6 years at least

i made pauses

aha ok

I made a pause during which I raised sheep in the French Alps

and other ecological activities

and reality kicked in?

the reality ?, i'm just a nerd, i must admit this weakness, i can't 
leave without technology

*can't live

hehe not enough buttons on a sheep I guess  ;-)

I tested sincerely, but to live without technology it is like living 
with the Middle Ages, one passes the three quarters of his time to 
produce his food and to make provisions for the winter .

that's why the stoneage was not known for it's artistic achievements

I've never heard of such a script, Steeve.

It does not seem to be on REBOLtech (a forerunner to REBOL.org). 
You could try some more detailed searches than I did if you want 
to look further
http://www.reboltech.com/library/scripts/
****

Sadly, a lot of good stuff gets published on personal websites, and 
when the enthusiasm for REBOL wanes, or the site is taken offline 
for some reason, the scripts are lost to the wider community.

Steeve, you can have a look at the scripts archive

http://www.rebol.org/cgi-bin/cgiwrap/rebol/ml-display-thread.r?m=rmlYCHQ

I forget whether it's possible to move backwards in the block I'm 
parsing?

yes, it is

... how? :-)

>> firsttime?: true parse [1 2 3 4 5][any [set v integer! p: (prin 
v if all [firsttime? v = 4][p: skip p -2 firsttime?: false]) :p]]
1234345== true

I'm not sure I get it. how does parse know how to deal with 'p?

p:  gets current parse position
:p  sets new position

but it must be in documentation somewhere

it does, but I still don't see it. does parse read the block at the 
end of the 'any block?

You can use it not just inside any block

but don't know any example why to use it without some rule like 'any

>> parse [1 2 3 4 5] [any [p: (probe p) skip]]
[1 2 3 4 5]
[2 3 4 5]
[3 4 5]
[4 5]
[5]
[]

gave up. two-pass is easier :-)

Here is Oldes example padded with comments:

firsttime?: true 
parse [1 2 3 4 5][
	any [
		set v integer! 
		p:   ; <-- set P to the current parse position.

       ; (This is the input series with the series index at the current 
       position.)
		
		(
			; Here inside the paren is normal rebol code 
			
			prin v 
			if all [firsttime? v = 4][

    p: skip p -2   ; <-- move the index of the series referred to by 
    P
				firsttime?: false
			]
		) 
		
		:p   ; <-- set the current parse position to P
	]
]

I am having a hard time with using REMOVE on a parsed string.

symbol: charset [#"a" - #"z" #"A" - #"Z" #"0" #"9" "_-?!*+~"]
nstr: "...aa.....a.....a.....h." 

parse/all nstr [
	some [
		symbol | end skip | 
		[

   here: ( probe here either none? here/1 [print nstr print "!!"  ][print 
   here/1 print nstr remove here here: back here]) ; :here skip
		]
		;:here
	]
] probe nstr

this just does an infinite loop... this is one of MANY twists I've 
put on the rules... (notice commented out :here)

and nothing works... if I set here to be the previous letter and 
then use skip in the rules... the first dot from nstr will not get 
removed... since we cannot go past the begining.

doh.... was about to give a better example... then I realise the 
error... there is nothing to match in the last rule, just an expression, 
so a no match is always matching nothing !

It's nice just thinking out loud once in a while...we're here for 
you Maxim.  Cerebration.  :)

it like saying the last rule matches the tail of the string.


Thus parse never gets "passed" the end cause my last rule matches 
the end, and thus prevents the parser from ever reaching it.

well, I was trying to say that I had not realized this was possible... 
and its quite cool... we can actually use that in some ways  ...


 make rules which make parse become an event handler for example ! 
  the moment you feed a string some value, parse will start treating 
 it...

and then fall back to silence... (just inserting a little wait in 
the loop will take care of cpu load)

it would be nice if the result from the expression could be used 
to determine if the rule is a match or not...

thus having (whatever expression TRUE)  would have allowed my previous 
last rule to match "everything else"

Off topic but...that was what intrigued me with SNOBOL and Icon...succeed, 
fail and a result.