[comp.sys.amiga.tech] IEEE libraries -- a solution

kurt@tc.fluke.COM (Kurt Guntheroth) (09/24/88)

What you need is a thing like an alert, which interrupts processing, but
let's the program continue to run.  Then you have a situation where (1) the
amiga hardware and OS look like they are very generous in the face of
errors, allowing nominally incorrect programs to run and (2) it makes
programs which have these problems look flakey.  Now the problem rests on
individual manufacturers to keep their programs from throwing up on people's
screens.  Competitiveness in the industry and PD programmer's pride will
tend to raise the standard of practice, but people won't be totally screwed
if they dont, and CBM doesn't have to go through unlimited gyrations for the
rest of eternity trying to clean up after messy programmers.

Sure it doesn't always work, like if you have an application which is
supposed to run unattended forever, but was written by hackers, but hay, if
you have bunches of bus errors in the program it won't work either.  Get
real.  It isn't impossible (or even difficult) to write good code on the
Amiga.  Its just harder than writing bad code.