World: r3wp

Josh, using the REMOVE-EACH very often is what makes your parse slow. 
A remove operation in the middle of a large string is slow, and you 
are doing many removes. That's why the others suggested using copy.

Thanks for the input.  I will have to play around with those later 
as I am trying to get this finished up and then I can go back and 
clean up the code. The data is minimal enough for the script to finish 
in under a second anyway.   Parse is pretty sweet.   Makes this much 
neater than the alternative

No worries.

I'm trying to copy some text from the position found iwhile parsing 
a document.
I'm using something like: 


rule: [some digit copy text to newline]    (--where "digit has ben 
defined as all digits 0 to 9)

 This copies eveerything after the digit. How would I copy the digit 
 itself as well?

would it not simply be....    to some digit    instead of what you 
have above?  I'll start playing around and see if I can be of any 
help (if you haven't already figured it out)

Not as easy as it seemed to be.  Will take more time than I have 
right now.

Is there a difference between using "to" and "thru"

yes

is this block parsing?

to goes to the point and thru includes the point

No

So to newline does not include the newline?

no it wouldn't

rule: [ digit copy text to newline skip ]
parse stuff [ some rule ]

digits: [ some digit ]
rule: [ digits ... ]

Graham, the digit String would be included in the copied text with 
this?

nope

because it matches digit and the cursor moves on

past the digit

Right. Anyway to capture the digit?

you can always do something like set n number!

rule: [ copy d thru digits  .... ]

He's using string parsing .. not block parsing

yeah can't use set then.

I'll try that Graham. Thanks

or

non-digits: complement digit
parse [ copy digit-text to non-digits copy text to newline skip ]

and correct syntax helps :)

>> str: "193920347REBOL ROCKS!^/"
== "193920347REBOL ROCKS!^/"

>> parse str  compose [some (charset "0123456789") text: copy text 
thru newline]
== true
>> text
== "REBOL ROCKS!^/"

Something like that?

he was looking for the number and the string though.

No

I have a text document with section numbers in front:

2. Hello
2.1 Hello Again
2.1.1 Hello already
3. Goodbye

I want the section number inclued in hte copy

It need not be included in hte same copy just as long as I can record 
it.

So you just want each line then really?

Well it gets a little more complicated.
some parts of the docment will be multilined.

I thought it would be a simple thing that I was missing. I may need 
to re-think the formatting of the document.

So even if something is multiline you would still want each line 
of the multiline correct?

Or do you mean a multiline might looks something like this:

2.1 Hello
       Goodbye

Where the second line doesn't have the preceeding number?

Yes and formating may need to be retained

Ahhh yes that gets a bit more complicated.

Paul, while you are there...
I was considering using Tretbase for this project

Excellent choise ;-)

Let me briefly explain where I'm going to see if you think its workable 
or perhaps a there is a better solution

k

I trying to put a set of Fire department related materials online.
THey are now in pdf

I'm converting them to text and reformatting them to parse

I want to hold each section in a seperate database record

So I can index for keywords and search and read only thse sections 
I need.

Photos and diagrams will also be stored.

Well, TRETBASE 1.0 is the only finished product right now.  So the 
only available TRETBASE app is 1.0 which is really not a multi-user 
solution.