World: r3wp

and the GC doesn't kick in too quick or it would be really slow  
(just try recycle/torture to see ;-)


so when you're doing serious work it REALLY grows... although it 
stabilizes


for example although stats often show 10MB... my OS tells me that 
its actually using 24 MB.  that will never shrink back down.

Is there a place for the newbie questions on parsing?

You've come to the right place.

I've created my very first script. The script loops through a list 
of email (Kerio) log files, extracts the IP addresses, compiles them 
in a list and adds them to a (Peerblock) list in order to limit incoming 
spam. I find rebol perfect for this.

So an entry in the log file starts like this: "[15/May/2010 17:59:56] 
IP address 190.101.1.10 found in DNS blacklist SpamHaus SBL-XBL..."

aye

Improve the script by reading only the latest entries in the log, 
and I pare the date like this: parse/all txt [thru "[" copy found 
to "]" ]

So I get the job done. This is the question: If I do parse/all so 
that spaces are not automatically included, how to I include the 
space in my parse rule?

A rule can be: "=," etc. How do I "escape" the space character so 
that I can include in my rule?

I've always used the spaces as delimeters

parse k [thru "[" copy date to " "]

I've used parse/all, and then used 'trim on the results.

Yes, that is exactly what I did and it works. However, for the sake 
of learning, how do I use the the space character as part of my rule?

don't see your point, show us the annoying rule...

Ok, I will. The point is that I want to include the space in my rule. 
Here's the example:

digits: charset "0123456789"

ip: [some digits "." some digits "." some digits "." some digits 
]

This finds the IP in the log entry. What if I have two ip addresses 
and I want to pick them at the same time: ip: [some digits "." some 
digits "." some digits "." some digits __space__ some digits ...etc]

And the IP addresses are separatered by a space?

My question really is, how do I escape the space character as one 
would in regular expressions?

you need parse/all

correct, and then, how do you place the space in the rule: {} ?

#" " or " " or { }

'space works too

parse/all is really your friend - no unwanted surprises ....

That's it? 'space? That is easy.

sorry , it only exists in R3

Yes, parse/all is great, and this is why I want to include the space 
not as a delimiter but as a character in the rule. As if, sometimes 
I want to find two strings separated by a character.

So #" " should do. I will try it. Thank you.

but you can make your own easly ;-)
space: #" "

>> a: "a b"

== "a b"

>> parse/all a ["a" " " "b"]

== true

My script works, but you know how it goes. Once a question creeps 
in the brain, it needs an answer. Thank you.

I would use #" ", or defined a space rule first: spaces: charset 
" ^-" (eventually include tab)

Thank you all.

some space 
is even better to my mind

some space 
is even better to my mind

>> spam: "[15/May/2010 17:59:56] IP address 190.101.1.10 found in 
DNS blacklist SpamHaus SBL-XBL..."

== {[15/May/2010 17:59:56] IP address 190.101.1.10 found in DNS blacklist 
SpamHaus SBL-XBL...}
>> replace/all spam "]" "" replace/all spam "[" ""

== {15/May/2010 17:59:56 IP address 190.101.1.10 found in DNS blacklist 
SpamHaus SBL-XBL...}
>> blk: parse/all spam " "

== ["15/May/2010" "17:59:56" "IP" "address" "190.101.1.10" "found" 
"in" "DNS" "blacklist" "SpamHaus" "SBL-XBL..."]
>> date: blk/1
== "15/May/2010"
>> time: blk/2
== "17:59:56"
>> ip: blk/5
== "190.101.1.10"

nice ....

trim/with "[]" is better to remove things...

rebol and logs are like bread and butter

yeah ... I used it often ... read/lines is your friend :-)

yep nothing in the world can beat this combination

Structured data like logs, but Rebol shines even when parsing unstructured 
data

Yep, this is my script to dig the IP's inside the log files. I was 
quiet excited to see how natural it was to write this:

digits: charset "0123456789"

ip: [some digits "." some digits "." some digits "." some digits 
]

newList: [] 
existingList: []

files: []
foreach file read %. [
	if find file "security.log" [
		split: parse read file none
		foreach it split [
			parse it [[ip] (append newList it) ] 
		]
	]
]

Then, I said, read only from the last read, and pare the date/time. 
I wanted to parse date AND time at the same time" [15/May/2010 17:59:56] 
But I hit a snag because of the space in between. I don't want date 
and time separater beause rebol can parse the string into a date-time 
easy. The space gave me trouble, and the brackets too.

I would write th ip rule more strictly.
ip: [1 3 digits 3 [#"." 1 3 digits]]

Using the charset did not work. So I did this: parse/all txt [thru 
"[" copy found to "]" ]. And said to myself, time to learn more and 
could not find resources.

g so helpful.

Thanks.

What is the problem in parsing date and time at the same time? I 
somehow don't understand, if the solution does what you need, or 
you need further help?