World: r3wp

Gregg, I used to use append/part to avoid the memory overhead of 
copy/part in many case.
Instead of doing like in the Ladislav's example. 
>> change/part something copy/part something-else range part.
I used  to do.

>> change/part something append/part clear #{} something-else range 
part.
It's not faster, but saves memory.


So, I don't know if it's a good idea to discard this use case from 
append and insert.

Esp in R3

(It saves memory, if the same code is called many times, indeed)

Re "it saves memory" - it is not expected to save memory (the GC 
should handle such code "smoothly")

Sometimes, I can't let the GC acts by himself because it's too late 
and tens of MB would be allocated for nothing.

But I agree it's rare cases, with intensive computations. Rare, but 
it exists.

It does not matter that it is rare: if you can find any unexpected 
of the GC, you should put it to CureCode as a major bug

unexpected behaviour of the GC

It's not a bug to my mind, the GC never acted smoothly.

maybe I just misunderstood, then. If it is not a bug, then you are 
actually saying, that the GC collects everything as expected? If 
that is the case, then why the trouble to "save memory"?

(I just tested, and your example is much slower than the code allocating 
and GC-ing the new string)

Yeah it's true, it's slower.

But if your app contains many loops with many copy/part at different 
locations, the memory may grow insanly before the recycle.
I saw that in many graphic apps with Rebol.

I saw that in many graphic app with Rebol
 - are you sure it was "before the recycle"?

Sometimes you don't want to put too much pressure on the GC, and 
sometimes you don't want to increase the total size of the pool too 
much, because that pool doesn't always get returned to the OS very 
quickly or at all. This is the motivation for additions like the 
/into option.

We'll see how much optimizations like that need to be undone once 
we have to adjust for task safety :(

the GC doesn't return the pool... only image data is ever returned 
AFAIK.

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