World: r3wp

Yes, that is what I was afraid of. (this is problematic, if you are 
not allowed to create new files) OK, Robert and I have agreed, that 
we keep INCLUDE case-insensitive (for file comparisons), and put 
the information into the documentation.

Ladislav, how about reading the root directory, find a camel-cased 
file, lower/uppercase it and ask if the file exists?

of course depending if the file doesn't happen to exist.

(not totally reliable)

again, this may not work if you are not allowed to read the root 
directory

nevermind, the solution we use for INCLUDE looks like sufficient, 
I will document how it works.

I guess also it's a problem for networked drives. The file sharing 
mechanism might offer incorrect information as to what the case sensitivity 
for the file system being shared, is.

Right, it is a complicated matter, that is why it looks better to 
use an "acceptable" solution instead of trying to implement a "perfect" 
solution

Could you try a variant on....
    all [exists? uppercase what-dir exists? lowercase what-dir]

....At least it does not require reads/writes outside of the current 
folder.

That is possible, but, unfortunately, not perfect as well. (Does 
not solve the case when the file system is case-sensitive, but contains 
both upper as well as lower case variants)

What I meant to write was:

all [exists what-dir? exists? uppercase what-dir exists? lowercase 
what-dir]

Plus then you need to check if info? is the same on all three.

I think that covers your case......But is not perfect either .... 
It fails If the what-dir path happens to contain no case sensitive 
characters.

It's tricky!

Agreed

Can't you infer whether the file system is case sensitive, case insensitive 
 or case insenstive but case preserving from system/version?

not if the includes are grabbed from a network resource, such as 
when running your R3 in a VM inside another OS and the source is 
stored in that other OS.

actually there is a way to know if the destination filesystem is 
case sensitive, but it requires a write operation.

Thanks for the explanation, Henrik.

you write two files with different case, using different data.  then 
read the first one, and making sure it doesn't give you the value 
of the second.

hehe... just saw sundanda's original post... which basically a play 
on my above post... it was out of scroll on my view.

Ladislav: I was going to suggest something similar as Sunanda, except 
by using [sort read %.] instead of [what-dir], then checking the 
first file with alphanumeric characters.  That way, if both upper 
and lowercase do exist separately, they'd show up in the list and 
can be adjusted for

Can you not assume, Ladislav, that you will have read access to user.r?
And use reads/info? for variants on that to check?

Graham, did you figure out the object issues? And are you using or 
have you tried the xml-object.r script?

Is this prefered result?:
>> sort [748x430 68x206 748x194 305x147]
== [305x147 748x194 68x206 748x430]

I take it back.. REBOL cannot have any idea what I want to do, so 
better to use compare function, like:
sort-pairs: func[block-of-pairs][
	sort/compare block-of-pairs func[a b][
		either a/x < b/x [
			1
		][
			either a/x = b/x [
				either a/y < b/y [
					1
				][
					either a/y > b/y [-1][0]
				]
			][ -1 ]
		]
	]
]

sort-pairs [748x430 68x206 748x194 305x147]
;== [748x430 748x194 305x147 68x206]

What object issues?

XML to objects from SUnday

get-obj-value: func[o [object!] p [path! word!]][attempt[do append 
to-path 'o p]]

Not optimized for speed though...

hmm... clever

So why am I walking the path?  lol

Oldes, exactly the use case to use case... 

case [
	a/x < b/x [-1]
	a/x > b/x [1]
	a/y < b/y [-1]
	a/y > b/y [1]
	'equal 0
]

(except I reversed some stuffs...)

yes, that's nice example where to use case:)

Steeve, that's sweet. "Case" doesn't show up in the dictionary and 
I had no clue we had such a thing. Very cool.

not in the dictionnary ? strange...

http://www.rebol.com/docs/dictionary.html

I use it a lot. CASE/ALL is also useful.

CASE is in the R3 dictionary:
   http://www.rebol.com/r3/docs/functions.html
But you are right -- it should be in the R2 dictionary too.

anyone know how to submit args when using 


r2.exe --do "probe what-dir probe system/script/args" --args  "r3.exe"

the above prints none

The help says this:
    -- args          Provide args without a script

There's a space between the -- and the word args, so I tried this 
and it worked:

   rebol --do '? system/script/args q' -- 'arguments here'

The help should probably say something like:
   -- <args>
to make it more obvious

doh... ok, I get it.

thanks.

Isn't this a rather erroneous message ?

>> now - 365
== 27-Oct-2009/23:03:45+13:00
>> now - 365.25
** Script Error: Cannot use subtract on date! value
** Near: now - 365.25

Yes.. Better might be "Cannot subtract decimal! from date! value."

email? [name-:-domain-:-com]
== true
>> email? [name-:-domain]..com
== true
>> email? [name-:-domain]...com
== true

Is this a bug?

The email parser is not very good.

You can convert anything to email.

I was going crazy trying to send to a long list getting errors...finally 
found the faulty address...how do you validate email then?

You should write your own parse rule, it should be failry simple. 
Probably there's already something on http://www.rebol.org

Amacleod - there was a discussion on ML or elsewhere, about how useless 
email dtype is, if it can't work as email RFC suggests. I was told, 
that I should not mistake datatype, with complicated parser for possible 
correct emails. I still insist - the datatype is useless that way. 
I found some grammar, I even posted it back at that time, but I think 
that someone at RT was simply too lazy to implement it :-)

the email datatype is not useful for different reasons: it can't 
be serialized properly.

either write your own parser ... or use my smtp challenge :)