World: r3wp

Cool... I had this idea with the comparators too but not to use pick 
and the level as the selector. Cool stuff!

:)

Has anybody noticed problems with files that have "%" in name?

Yes, can't open them in WinXP.

No, yes you can.

read %"Hi%there.txt"     <-- this filename works

yes, but load mold %"Hi%there.txt" does not

>> load mold "Hi%there.txt"
== "Hi%there.txt"

what version of rebol, what os ?

1.3.2 on WXP

no, sorry, you're right. I missed the initial %

I think % should be automatically translated to %25 (like space is 
translated to  ) to prevent these problems

It does not mold into a loadable string. --> RAMBO.

OK, I'll post it

Note also this bug!  http://www.rebol.net/cgi-bin/rambo.r?id=3189&

well, that's really strange. see this >>
>> load mold to file! "[s-:-a]"
** Syntax Error: Invalid email -- %[s-:-a]
** Near: (line 1) %[s-:-a]
>> load mold to file! "[aas-:-df]"
== ª[s-:-df]

everything in range from "aa@.." to "ff@.." produces the second result

Add this information with the link to #3189 to your report. They 
should insert it into the original bug report.

these ways can be used to circumvent the filename character problems 
if needed:
load {%"aaa%aa"}
load "%aaa%25aa"

how to catch following error? error? try [to-date 29-Feb_2006]

ok, putting date in a string helps ...trying to catch leap year ...

I don't like it - why rebol parser interrupts me so fast?

petr, in the above case (without the quotes), the error happens before 
rebol gets to evaluate the TRY.

you need to put the LOAD or DO that are loading that code in a try 
block.

it does not seem to work:

error? try [load 29-Feb-2006]

I would prefer 29-Feb-2006 error, as well as e.g. error? try [load 
380.250.250] being a bit more relaxed in interpreter ...

how can I catch such syntax errors?

what is your problem?

error? try [load "29-Feb-2006"] ; == true

the problems is uncatchable error

I am not talking about string ....

I am not sure I can meet with such situation in real-life :-) I just 
got asked by Bobik. The thing was, that in sqlite date field there 
can be invalid date. Now I am not sure how is the conversion done, 
if via string, but if you simply type such invalid date in console, 
it can't be recovered, and that is my objection in general ...

shouldn't we be always able to recover from whatever error happens?

To be executed, a script is loaded in a whole. So each values is 
loaded/binded and your error appears at this time, not while the 
expression is evaluated.

do you mean that I can catch the error during load? but why loading 
value itself fails?

what uncatchable error?

try to type in console 29-feb-2006 ....

although it is invalid, I thought that by error? try [29-Feb-2006] 
I will be able to recover eventually, which is not the case ...

>> if error? try [ load form 29-feb-2006 ][print "date format error" 
]
** Syntax Error: Invalid date -- 29-feb-2006

** Near: (line 1) if error? try [ load form 29-feb-2006 ][print "date 
format error" ]
>>

>> if error? try [ load "29-feb-2006" ][print "date format error" 
]
date format error
>>

Doesn't like the 29-Feb-2006 as a date string

date type!

looks like a bug?

Looks like it.

Does not like 32-may-2006 too. Isn't this more a feature than a bug?

error? try [29-Feb-2006]

 is "word! word! [what-is-this?]". Reol has no idea what to do with 
 "error?" at that time.

well, but Volker, anyway, we got to state, where we have non-recoverable 
interpreter state, don't we?

I know the date is invalid, but .... the same goes for tupple, e.g. 
380.250.250

>> 380.250.250
** Syntax Error: Invalid tuple -- 380.250.250
** Near: (line 1) 380.250.250

you are not at interpreter state at that time. think of 'load finding 
an error at compile-time.

I know, I just don't like the fact, console is not safe from such 
errors ..