World: r3wp

using real encryption does not make any difference... but anyway.

that is what I'm saying... so why waste time with some complicated 
scheme to store the password?

I mean Gabriele, no system in the world is ultimately secure.  The 
point is only to make it unfeasible.

cause its going to be requested from every user the first time they 
have to "re-login"  ;-)

I don't think my point is clear...

I'm saying that it's a waste of time to try to make it "more secure"

or "more unfeasible"

just use encloack and obfuscate it so that it does not jump to the 
eyes.

if someone *wants* to get your password they will get it. so why 
bother?

to make the client happy (the one paying for the application  ;-)

I mean paying me to build it... not the end-user ... ;-)

is the client paying you to use a machine specific id and some secret 
encryption scheme?

he'll want the stored password  toat least require effort and thus 
a real cracker to break the binary. 


this feature will be added later, if ever, it wont for initial public 
release specifically for the reasons you talk about and which I already 
had the same conclusions.

toat = to at

this discussion just re-inforces my POV wrt not including the password 
save feature for now.

what does you make presume that he'll want that? and, what does "real 
cracker" mean?

What's the quick way of getting the root directory ?

This seems tortuous 

rootdir: to-file rejoin [ "/" second parse/all what-dir "/" "/" ]

copy/part what-dir 3

is shorter

On Windows: read %//

sorry ... I meant I want %/c/   ... and not read the directory

ie. want the path

Then your second method is best, unless you are on a UNC path, then 
try this: copy/part find/tail next what-dir "/"

Sorry, this:
rootdir: copy/part rootdir: what-dir find/tail next rootdir "/"

Does this do it?
    clean-path %//

It should. It does on R3. Let me try it on R2.

Yup. On R3 it's slower though, sincee clean-path is mezz.

On R3 the fastest way is this: head clear find/tail next what-dir 
"/"

http://rebol.wik.is/Cheyenne/Upload-file.rsp

don't think I'll need UNC path support :)

I use it a lot :)

on a web server?

Nope - remote file manipulation. UNC paths are for Windows shares, 
not web shares.

Ratio is giving me good opportunities to sharpen my skills. While 
writing a post, I bumped into this:

http://www.rebol.org/view-script.r?script=substr.r

What do you think? :-)

From the script header: Purpose: "Working around string series"...I 
think that this is shooting yourself in the foot.

Don't you think this is a little inconsistent?

>> a: ""
== ""
>> a/1
== none
>> last a
** Script Error: Out of range or past end
** Near: last a
>>

IIRC, Carl explained (at least) once that this behaviour is different 
on purpose. Using path notation with an index value or PICK should 
return NONE while using the prefix notation FIRST, SECOND,...LAST 
should return an error. So you have the choice to either silently 
handle missing values in series or raise an error!.

In R3 it is consistent.

>> a: ""
== ""
>> a/1
== none
>> last a
== none

SYSTEM/SCHEMES/FTP/PASS is a none of value: none
  set-net ['abc]
  ? system/schemes/ftp/pass
SYSTEM/SCHEMES/FTP/PASS is a string of value: "abc"

the documentation says "The first value is your email address and 
it is used when sending email and connecting to FTP. This value is 
stored in the REBOL system object at: SYSTEM/USER/EMAIL".

I don't think it's a good idea that the ftp password will be set 
to the email address as well, "used when connecting to FTP" maybe 
it should set the user instead

that's the way it used to be done

the convention for anonymous FTP is to provide "anonymous" as the 
user and the email address as the password.

I am having a very hard time build a low-level function which reduces 
only bound words.

the bound? function is useless, it returns the global context when 
it hits a new word, cause it defines the word as it scans it.

value? doesn't see the word, only its label, which in parse rules 
collides heavily with standard rules.

any one can give me ideas?

unset? always returns false, cause it pretty much only matches non-returning 
functions like print, but you have to evaluate them to know, so its 
useless again.

so far this seems to be impossible to resolve in R2    >:-(

can you give an example of the expected result ?

false == (some magic trick) first load "[any]"
true == (same magic trick) first append [] in system/words 'any


the first is just an unbound word, using the string just makes this 
explicit beyond doubt.
the second is the actual word func. added to a block.