Hi Romano, funny. It looks, that the error is detected when a string becomes a result:
type? try [b] ; == string! b 1 ; == 1 Ciao -L I think, that this kind of "checking" does not work very reliably. ----- Original Message ----- From: "Romano Paolo Tenca" Can someone explain this to me? a: "a" ; == "a" b: tail a ;== "" remove a;== "" a ;== "" b ;== ** Script Error: Out of range or past end try [b] ;== ** Script Error: Out of range or past end ;until here all is OK, but then: error? try [b] ; == false Is it an error? bug? --- Ciao Romano -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
