World: r3wp

aha, I would like it better to.. if/else is gard to read.. but I 
didn't know it exists :)

thanks

great, it all works now

What about using:
 **FAILED**^/ expected: 
 
instead of:
 **FAILED**
 newline " expected: "

>> ? newline
NEWLINE is a char of value: #"^/"
>> ? lf
LF is a char of value: #"^/"

Thanks Oldes, I didn't know for ^/ and I also didn't know that I 
can type "?" instead of "help"

and ?? too

sometimes can be usefull :)

:) I didn't know for this too.. but I did >>? ?? to find out now 
:)

...what it does . thanks

Example; say you are trying to debug an app and you have to print 
the contents of a word to the screen.
say you set the word 'value to 10
displaying value to the console can be done by using; print value
returns the result; 10


where as using  "?? value " instead, would return the word name with 
the value of the word beside it
value: 10


This prevents you from needed to add debugging code like'
print ["Value: " :value]

Welcome Ben Bran...


This world is a crazy wonderful place of amazing people that can 
probably help you with any REBOL question you might have.

Yes, I suppose my newnewss is really glaring... Thank You Reichart!

These ppl can help you with many things ... from religion, to compose 
music :-)

Yes and I need all the help I can get Pekr  :-)

New to REBOL?

Read a Dummies book on it about three years ago.  Been watching it 
ever sense.  With R3 coming out, I'm going to give it a serious look.

Good. R3's gonna be cool. There is just still lots of work on it 
:-)

But - we will be able to cooperate and hence influence its development 
...

Yes, thats why I signed up..... so hope to get more involved with 
the development....

time permitting....

I see, your name is Ben Brannen...

Even before R3 comes out, you will find R2 pretty amazing...

And you may like thge new English translation of a French book; translated 
by Peter Wood, who is here as well. It's on lulu.com

Wanted to say Welcome to Janko and BenBran.

Thanks Paul

Your welcome.

I have another question about parse, if I may.. I am trying to make 
a parse block that will uppercase all letters after the . ! or ? 
. I did it just for dots, but I can't make it for all 3  ( one alternative 
is to call parse 3 times each time with different separator char. 
The problem can be observed here, and happens because [ A | B | C 
] pattern first looks for A and if it doesn't find a checks B , which 
means it will skip B if A is after B. Is there any way to say "use 
any of those chars - *whichever comes first" ? .. example where you 
can see the  problem:

== true

>> parse "A.B!C.D." [ any [ [thru  "." | thru  "!" ] mark: (print 
mark ) ] ]
B!C.D.
D.

>> parse "A.B!C.D." [ any [ [thru  "!" | thru  "." ] mark: (print 
mark ) ] ]
C.D.
D.
--- in first case it skips the C in second it skips the B ..

this is my code to uppercase after scentences : parse X [ 
				ANY [ [ thru "." | thru "!" | thru "?" ] 
						mark: ( uppercase/part trim mark 1 insert mark " " ) :mark 
				] 
			]

It works if I have just one kind of separator of if I have them in 
this order for example "a.b.c.d!e?" if I have ""a.b.c.d!e?f. "  it 
will skip the ! ? and produce "a. B. C. D!e?f. "

because it will skip over ! and ? to the last "."

hmm... do this 

parse source [any [["!" | "?" | "."] mark: (do something) | skip 
]]

Thanks Reichart.  Yes a good old Irish name (spelling changed when 
got to America).  If Ihave my numbers rights,  I'm 4th generation 
German/Irish/Swedish American and my daughter can add Spain and Mexico 
to her list.   R2 did keep my interest these years.  I'm somewhat 
at a loss to

oops typo sorry....

BenBran, you can click the pencil above the text edit field to make 
multiline messages.

Thanks, Thats much better.

Steeve: I solved it by doing 3 passes , one for each character (.!?) 
. Performance is not that important here as it's a client , but if 
it's possible to do it in one pass I would certanly like to learn 
about it. I will try what you proposed, Thanks!

str: "a.b.c.d!e?f. "
chars: complement charset ".!?"
>> parse str [any chars tmp: to end (uppercase tmp)] str
== "a.B.C.D!E?F. "

>> parse str: "assd.asd!d" [any chars tmp: (uppercase tmp)] str
== "assd.ASD!D"

Hi. I am struggiling to understand parsing & hoping for some pointers.

I have read everything I can find but still cant seem to use parsing 
for basic extraction of information from a number of lines (or even 
a single line).  This is what I am trying to do & would love sme 
help or links to documentation I may have missed please.


lines: {junk wanted line1 contentA rubbish
junk notNeeded line2
wanted line three content B rubbish
}
;I want to extract
;wanted line1 contentA
;wanted line three content B


;That is to say everything between "wanted" up to "rubbish" but including 
"wanted"

Thanks, /\/\

Another (maybe foolish) question please.



I am trying to use this script to help me understand the use of parsing 

to extract data from files. If I paste the script into my REBOL/View 
console it pastes in the script ok, but the examples do not work.


This seems very common with a lot of the scripts in this library 
and is a problem I have been fighting with for several days.

This is what I get.
>> ini: parse-ini-file %/c/windows/win.ini
** Script Error: Out of range or past end
** Where: parse-ini-file
** Near: append last current-section parsed-line/1
append
>> 


Am I pasting the script & examples to the wrong type of console or 
something?

I feel it must be something I am doing as so few of the example scripts 
work for me.

Thanks, /\/\

You need to provide some rules for what you want and what you consider 
rubbish.

there has to be a pattern that you recognize to determine what is 
what.

>> extract: copy []

== []

>> parse lines [any [["wanted" copy temp to "rubbish" (append extract 
temp)] | skip ]]
== true
>> extract

== [" line1 contentA " " line three content B "]

Have you read this - http://www.codeconscious.com/rebol/parse-tutorial.html

Hi, thanks very much for the fast replies. 

I have read the parse-tutorial and it seems very good for understanding 
how to create rules that will match patterns, however I only found 
one brief section that described using "copy" to extract the data 
from the line, rather than just confirming that a match was found 
(or not). I tried to use the copy examples but evey time I modified 
them I ended up with errors as I don't really understand how they 
work.


Peter, thanks for your example, it does almost what I want but the 
result in 'extract' does not contain the part of the string matched 
by "wanted". In my simple example I could just append the word "wanted", 
but in a real world case I would be using a patern match to find 
the "wanted" key word.


I also want to develop the code further to search for a different 
set of matches if the first set is found, in your example I am unclear 
where the block is that is performed if the string is found.  

Thanks very much for your help. /\/\

There's a bit about COPY in PARSE here:
http://www.rebol.com/docs/core23/rebolcore-15.html#section-7.3

mhinson - dunno if somebody already replied to you, but 'copy works 
quite fine. The trouble is, when you change parsed string in paren. 
You have to put markers there, and return to correct position ...

Mike: A small change will include wanted:

>> extract: copy []
== []   

>> parse lines [any [[copy temp ["wanted" to "rubbish"] (append extract 
temp)] | skip ]]
== true
>> extract
== ["wanted line1 contentA " "wanted line three content B "]

The code that is executed in a parse rule is enclosed in parentheses 
().

So the parse rule that finds wanted.... is

 copy temp ["wanted" to "rubbish"] (append extract temp)


The copy copies the part of the input that matches from the start 
of "wanted" to the start of "rubbish". 


Then the Rebol code (append extract temp) is executed. (I would normally 
write the Rebol as - insert tail extract temp - as it is faster than 
append in Rebol 2.)