Path: utzoo!utgpu!water!watmath!clyde!rutgers!cmcl2!brl-adm!umd5!ames!pasteur!ucbvax!USU.BITNET!FATQW
From: FATQW@USU.BITNET
Newsgroups: comp.sys.amiga
Subject: Re: A bug in Lattice 4.0
Message-ID: <8802200132.AA00921@jade.berkeley.edu>
Date: 20 Feb 88 00:27:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 32

This is what I'm quite sure is the case - don't trust me though!

The CLI doesn't clear the CTRL-C sigbit before it starts a program.  If it
did, the problem would be solved.

The normal BCPL AmigaDOS commands which honor CTRL-C probably have some kind
of startup code which automatically clears the CTRL-C sigbit before going on.
The Lattice startup scripts don't do this.  I don't know about Manx.  So
you can get CTRL-C's that were pressed before the program was started.

Three solutions I can think of.

Change the CLI (in the next KS/WB release) to clear CTRL-C before starting
programs.

Edit the startup code you use to clear the CTRL-C bit before starting the
main program.

Put something like this at the beginning of main():

        SetSignal(0,SIGBREAKF_CTRL_C);

Yes, I know the RKM states this as dangerous, but I really don't think it
would be dangerous to use in this way, or other `controlled' ways.
(you define `controlled'.)

                                Bryan

        Bryan Ford                    //// A computer does what \\\\
Snail:  1790 East 1400 North         //// you tell it to do, not \\\\
        Logan, UT 84321         \\\XX///  what you want it to do. \\\XX///
Email:  FATQW@USU.BITNET         \XXXX/ Murphy's Law Calendar 1986 \XXXX/