World: r3wp

Great! A case statement! I have been waiting for that!

I like the functionality too. nice!

if you rename PIF to CASE (in the PIF source too), you hardly can 
find a difference

is there a way to use a function with a refinement as a word?

something like:

do-a-function either condition ['ref][none] <arguments>

as opposed to the clumsier:


either condition [do-a-function/ref <arguments>][do-a-function <arguments>]

No good ways. You can build a path and do that.

Dialect

You can try multimethods.r

And have two singleton methods on the argument ref.

for own functions once i had an idea, but never really used:

f: func[/a va /b vb /opts blk][
 if opts[do bind blk 'opts] 
 ?? a ?? b
]
f/opts [a: 5]

hmm... a bit confused about the BIND part...

it binds the opts-blk to the locals. then you can set the locals 
from the caller.

still confusing, but

ref-a: none
val-a: "A"
ref-b: true
val-b: "B"

f/opts [a: ref-a if ref-a[va: val-a]  b: ref-b if ref-b[vb: val-b]]

but then it needs a composeto avoid name-clashes. maybe not the best 
idea.

you lost me :-) but it's ok, I'll try something with build-path...

You can do this:

do to-path reduce ['do-a-function either condition ['ref][none]] 
<argument>
but if it's less clumpsy, you deside!

; Try this way, no reduce or to-path...

do either condition ['do-a-function/ref] [:do-a-function] <argument>

; Or this
do pick [do-a-function/ref do-a-function] condition <argument>

Graham:

>> word: to lit-word! 'literal
== 'literal
>> parse [literal] [word]
== true

lots of different solutions to my problem... thanks everyone :-)

a comment on ATTEMPT. I think it's a wonderful function, but don't 
overuse it because it can make your code hard to debug when nothing 
happens where there should be an error.

true

i only use it for single calls.

Steve, when it comes to SIXTH, I wouldn't worry too much.

Is there a way to set and read windows environmental variables ?

'get-env ?

thanks.

Does it work ?

works with "path" ..

env

'scuse me...

Perhaps I need to reboot for rebol to pick up user env variables 
?

>> get-env "APPDATA"

== {C:\Documents and Settings\Gabriele Santilli\Dati applicazioni}

I had to reboot for this to work.

You mean, you set a new user env variable, and rebol wasn't able 
to pick it up straight away ?

logout and login probably sufficient

didn't try that ...

i'm running into a strange issue with the prerebolizer... it is taking 
a part of one line from my main rebol file and then a few blocks 
of another rebol file and overwriting another seemingly random rebol 
file with this data... has anyone run into this problem or have any 
idea what could be causing the problem?  i am using Preprossor 2.0.0

I haven't seen that Robert. Can you narrow it down to a very small 
example?

>> o: make object! [time: does [now]]
>> third o
== [time: func [][now]]
>> reduce third o
== [7-Dec-2005/3:23:23+1:00]
>> third o
== [time: 7-Dec-2005/3:23:23+1:00]

>> o: make object! [time: does [now]]
>> third o
== [time: func [][now]]
>> reduce copy/deep third o
== [7-Dec-2005/3:25+1:00]
>> third o
== [time: 7-Dec-2005/3:25+1:00]

Why is the block not copied?

ah, using GET instead of THIRD allows me to copy it

I have one question regarding security - can actually rebol words 
be secured/protected? I noticed, when looking at get-net-info and 
trying to execute it, that get-reg is probably being unset internally 
after get-net-info gets executed. Isn't it sign rebol's security 
model is not sufficient?

I am not trying to say that we need modules, but I would like to 
know your opinion? Can some rebol word/value be really protected? 
We have 'unprotect available, so actually what is 'protect good for?

can I e.g. create word in context, which would be visible only in 
terms of such context? Being it value, function, whatever, prevented 
to be outputted by 'get, 'probe, 'print, 'source and other functions?

Henrik: what happens there is that the word TIME is set to the result 
of the function.

AFAIK not. 'protect is for debugging AFAIK.

But i can work secure if you use 'secure. The way is, as long as 
i dont touch user-data, i am secure. Thats why rebol has get-reg 
on startup, no user-code loaded, no harm possible. Before i touch 
user-code (or data), i tighten security as much as possible. unset 
dangerous words (if i am paranoid i disable "make struct!". I use 
secure to restrict file-access only where needed, disable shell and 
library, maybe network-access. A script/bug can not undo this things, 
and IMHO that is quite secure.