mwm@eris.BERKELEY.EDU (Mike (My watch has windows) Meyer) (09/15/87)
In article <165@jc3b21.UUCP> fgd3@jc3b21.UUCP (Fabbian G. Dufoe) writes:
< As I understand it, that is exactly how Lattice handles the problem
<with version 3.10 of their C compiler. I believe you have the option of
<disabling that code, but the default is to trap BREAKs (^C) and put up a
<requester asking if you wish to continue or abort. Doesn't that pretty
<well solve the problem for Lattice users?
The description of what happens is exactly correct. By default, BREAKs
cause a requester asking if you really want to abort; you can change
that either through some Amiga-specific routine (onbreak), or through
the ANSI signal() function.
The first problem is that the Lattice exit() won't clean up after
things you allocated other than through the Lattice libraries. Like
closing windows, etc. This is solveable via the onexit() hook from
ANSII (I'm about to rewrite some code to use that - why didn't I think
of it before!). But your program still has to take care of things.
The other problem is that it won't stop code that isn't checking for
the BREAK signals. The Lattice libraries do this whenever they do
low-level IO. But if you're hung in a tight computation loop, it
doesn't buy you anything at all.
<mike
--
Kiss me with your mouth. Mike Meyer
Your love is better than wine. mwm@berkeley.edu
But wine is all I have. ucbvax!mwm
Will your love ever be mine? mwm@ucbjade.BITNET