Re: Error checking.....a good way of doing it (was: Initializing code in a module...)

2003-07-15 Thread Jeff 'japhy' Pinyan
On Jul 15, Hamish Whittal said: >1) Keep a central 'repository' (a hash) of all errors that can be >generated in all the different modules and pass the error to a function >that decides what error to run. That sounds like a good idea. >package Common; > >sub ERRORSTRING { > >

Error checking.....a good way of doing it (was: Initializing code in a module...)

2003-07-15 Thread Hamish Whittal
Well thankyou all for the replies. (This must be one of the best lists I subscribe to.) Now, why I wanted to run the code each time I called the module... I am wanting to do error checking within my code. I am experimenting with the best ways to do this. 1) Keep a central 'repository' (a hash) of