Hi Cor,
|| That "try catch end try" was my first thought, but someone
|| told me that it is bad programming.
I only gave it because Z isn't satified yet.
Using Exceptions for normal coding is seen as bad practice for a few
reasons as far as I know.
Firstly because they should be reserved for things that actually <are>
exceptional rather than used for doing 'tricks'.
Secondly the mechanism they use is, at a lower level, a bit like electric
shock treatment - in this case a jolt to the stack. That's if I understand it
correctly. Using C, under Unix, there was a function called setjump() which
would put a marker in the stack. When something bad happened, you could call
longjump() which would 'wipe out' the stack and return control directly to
where setjump() had been called. I'm sure that it's not that crude with
Exception handling but it <is> an abnormal interruption.
Thirdly, they are comparitively slow to execute - definitely not for heavy
use within the regular flow of program logic.
|| ... I alway says you have bytes which contains bits.
Talking of bites. I need to go and have a bit to eat.
See you,
Fergus