CompuServe Messages

>>I agree in some facets a weight can be put on things (say the difference between an malfunctioning ATM bank machine vs a malfunctioning pacemaker) but still, I'd make the effort for both of them.<< Agreed. What I meant is that, very often, you have an error that will never be seen during the useable life of the program. When I made the calculation library for my accounting package, there was a typing error in the division routine. I found a way around this before I discovered the bug. Therefore, there was an error in the program and yet, the program behaved correctly. The error was this: moveq.l #0,d0 moveq.l #0,d0 it had to be: moveq.l #0,d0 moveq.l #0,d1 For a reason that still deludes me I only found this error more than a year after having written the routine when I was looking for something else. And yes, I also always do the best I can to avoid errors. Bart Van Bockstaele at 100574.2352@compuserve.com … On AutoPilot and Amiga all the way from Belgium NOT from Mars!…