Hello [EMAIL PROTECTED]! On 27-Giu-00, you wrote: l> if the error occurs, it surely is fired and everything goes as l> expected. But there is a legal way how to obtain an error l> value: l> e: make error! {some error} l> f: try some-code l> After any of these expressions occurs, you get an error as a l> normally computed Rebol value. How would you expect the l> following code to behave? [...] I think you have a valid point here. I still hope to hear the words of RT... Regards, Gabriele. -- Gabriele Santilli <[EMAIL PROTECTED]> - Amigan - REBOL programmer Amiga Group Italia sez. L'Aquila -- http://www.amyresource.it/AGI/
- [REBOL] A data inconsistency Re:(4) lmecir
- [REBOL] A data inconsistency Re:(5) giesse
- [REBOL] A data inconsistency Re:(6) lmecir
- [REBOL] A data inconsistency Re:(7) giesse
- [REBOL] A data inconsistency Re:(8) lmecir
- [REBOL] A data inconsistency Re:(9) giesse
- [REBOL] A data inconsistency Re:(10) lmecir
- [REBOL] Re: A data inconsistency Re:(10) giesse
- [REBOL] A data inconsistency Re:(12) ingo
- [REBOL] A data inconsistency Re:(13) lmecir
- [REBOL] Re: A data inconsistency Re:(12) giesse
- [REBOL] Re: A data inconsistency Re:(12) giesse
- [REBOL] A data inconsistency Re:(10) anton
- [REBOL] A data inconsistency Re:(11) ingo
- [REBOL] A data inconsistency Re:(12) anton
- [REBOL] A data inconsistency Re:(13) ingo
- [REBOL] Re: A data inconsistency Re:(10) giesse
- [REBOL] Re: A data inconsistency Re:(7) blazs
- [REBOL] A data inconsistency Re:(4) giesse