Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!haven!uflorida!gatech!ncsuvx!mcnc!rti!sas!walker
From: walker@sas.UUCP (Doug Walker)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Two Questions
Message-ID: <1018@sas.UUCP>
Date: 28 Apr 89 15:12:32 GMT
References: <10384@cit-vax.Caltech.Edu>
Reply-To: walker@sas.UUCP (Doug Walker)
Organization: SAS Institute Inc, Cary NC
Lines: 20

In article <10384@cit-vax.Caltech.Edu> bdiscoe@tybalt.caltech.edu.UUCP (Ben W. Discoe) writes:
>First question:  In the same line as the discussion of turning off those
>obnoxious lattice "ads" - 
WHICH, by the way, are LEGALLY REQUIRED if Lattice is interested at all in
keeping copyright to the program...

> Is there any way to get rid of the Ctrl-C break
>requester code?  I couldn't find a way to do this in the manual (V 4.0)
>Is this a result of linking with c.o?

To get rid of Ctrl-C code, put a function in your program called ChkAbort()
that simply returns 0.  This will take precedence over the ChkAbort() func
in the Lattice libraries and no requester code will be pulled in.  If you
simply do a signal() or install a break handler, all the Ctrl-C code will
be pulled in only to be disabled by your program.

You can check for the presence of unwanted library code by looking at
the map of your program - use the 'map hsfx' option on BLink.

--- Doug