Path: utzoo!utgpu!water!watmath!clyde!att-cb!att-ih!pacbell!ames!pasteur!ucbvax!ernie.Berkeley.EDU!carlson
From: carlson@ernie.Berkeley.EDU (Richard L. Carlson)
Newsgroups: comp.sys.amiga
Subject: Re: Lattice 4.0 Problem or bug?
Summary: Not really
Keywords: User Abort Requested
Message-ID: <23625@ucbvax.BERKELEY.EDU>
Date: 16 Apr 88 04:07:13 GMT
References: <195@dsacg2.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: carlson@ernie.Berkeley.EDU.UUCP (Richard L. Carlson)
Organization: University of California, Berkeley
Lines: 28

[I hope I'm not beating a dead horse; I'm 600 messages behind and have to
 trust readnews's telling me there are no other followups]

In article <195@dsacg2.UUCP> nor1675@dsacg2.UUCP (Michael Figg) writes:
>I've been getting this requestor "User Abort Requested" about 30-40% of the
>time when I compile with Lattice 4.0 (lc -L filename.c). This requestor jumps
>up as soon as I start the compile (If is going to appear at all) ...

The problem is with the CLI -- if you try to interrupt a running program, and
that program does not properly handle the interrupt, the next program you run
will inherit the interruption flag.  John Toebes recently explained why this
problem can't be solved by causing compiled programs to simply clear these
interruption flags when first starting up:  the program can't tell the
difference between a "leftover" ^C and a ^C typed while the program is being
loaded, and you definitely don't want the latter to be ignored.

By the way, this behavior is not new to Lattice 4.0:  the same thing happened
to me many times with version 3.03 -- except that that version didn't have
the nice "user abort" requesters; programs simply quit immediately without
explanation.

I'm curious, though ... it seems all of the complaints about this have come
from Lattice users -- does Manx default to not handling ^C interruptions? or
clear out the interruption flags when a program first starts to run?

  -- Richard
    carlson@ernie.berkeley.EDU
    ...!ucbvax!ernie!carlson