World: r3wp

I won't be able to grab the PID without some Windows API I guess

you don't necessarly need  of the PID.
On which OS are you running your apps ?

oh windows !

if it's to kill the processes, then you got this command http://www.tech-recipes.com/rx/446/xp_kill_windows_process_command_line_taskkill/

very versatil

Windows 2003 and 2008

you should have the same, no ?

I mean, to be able to kill a process just with its name

except I am running multiple processes with the same name

I really only need to remove a process if it has died ... and is 
sitting at the rebol error message

just rename the exe

Sysinternals has better ps utilities, which can do a better job of 
killing process if need be.

I need to do something like this:

>> a: context [b: context [c:1]]
>> get in a 'b/c
== 1

Is there some way to do this?

the only chanined solution which comes to my mind is:

 get in get in a 'b 'c

having,
>> to-path [a b c]
== a/b/c

you can get it with:
>> do to-path append [a] 'b/c
== 1

>> do head clear change change '_/_ 'a 'b/c
== 1

Pekr: that's what I need to avoid.

>> a: context [b: context [c: 1]]
>> do bind [b/c] a
== 1

is that more like what you want?

haha, you won

Ladislav, exactly! Thanks

my line of thoughts was .... hmm, I would somehow have to bind b/c 
into 'a's context, but  .... then I never know, how to use bind :-) 
Cool solutions, both from Ladislav and Steeve ....

Actually, Pekr, your solution has to be used in some cases in R2, 
since the support for get-paths is missing

I don't know much about it, I just remember that path evaluation 
has changed with some R2 version - from more to less "aggressive" 
... does it for e.g. mean, that with earlier versions of R2, it was 
possible?

Ok, so now let's make it bit more complicated :)

I have the a object and  for example
>> p: make path! [b c]
and I need something like
>> do bind [p] a
== 1

do bind reduce [p] a

or,
>> do head insert p 'a

:-) ... amazing :-)

(i'm sorry for such a newbie questions, but I'm ill and my brain 
refuses to work :-)

...does it for e.g. mean, that with earlier versions of R2, it was 
possible?...
 - no, it is possible in R3

jdishun (and other fans of named functions) - check http://www.rebol.org/view-script.r?script=named-func.r

That's nice, finally something to point to when that question comes 
up again.

ah, those named functions are brilliant

maybe we should add special handling to bind so that each function 
is automatically passed a handle to refer to itself

we could call it ..... self!

/apr1

:-D

:)

NAMED-FUNC is excellent though. A great REBOL example. Thanks for 
doing that Ladislav.

Rebolek couldn't you have done this in your first example:
>> a/b/c
== 1

No no no. It's again the rules. You have to find the weirdest way.

Ahhh...

Is there is better way to code the following idiom:

	foreach [from to] [
		"&" "&"
		"<" "&lt;"
		">" "&gt;"
		"^/" "<br>"
	][
		replace/all string from to
	]

I'm using this much too frequently for my own liking ;)

there are faster algorythms, if you are managing very large files, 
but they require a bit more code and/or use of parse.

still, replace is pretty fast... I don't know if the parse approach 
will be faster with only 4 items to replace.

then again, if your source string has many of the origin ("from") 
strings the parse could still be faster... I guess it largely depends 
on the size and shape of the data you are manipulating.

Steeve :))

Paul - no. The object is anonymous and I know only the b/c part.

Ashley, I've done parse-based REPLACE funcs, and a simple TRANSLATE 
func, but I haven't generalized and dialected them the way I want 
to either. This week is busy for me, but if you want to collaborate 
on something, let me know. I think it would have a lot of value.

I use a variant of this:

sanitize: use [chars encode][
	chars: complement charset {&<>"}
	encode: func [txt chr][change/part txt chr 1]
	
	func [text [any-string!]][
		parse/all copy text [
			copy text any [
				text: some chars
				| #"&" (text: encode text "&amp;") :text
				| #"<" (text: encode text "&lt;") :text
				| #">" (text: encode text "&gt;") :text
				| #"^"" (text: encode text "&quot;") :text
			]
		]
		any [text ""]
	]
]

Provides a bit of scope for expansion...

Though it's admittedly bigger...