home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!att!linac!pacific.mps.ohio-state.edu!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!agate!stanford.edu!rutgers!cbmvax!cbmehq!cbmger!edohwg!heinz
- From: heinz@edohwg.UUCP (Heinz Wrobel)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Breaks
- Message-ID: <heinz.03a6@edohwg.UUCP>
- Date: 30 Aug 92 10:54:52 GMT
- References: <5215@tuegate.tue.nl>
- Organization: Edotronik GmbH
- Lines: 27
-
- In article <5215@tuegate.tue.nl> marcelk@blade.stack.urc.tue.nl (Marcel van Kervinck) writes:
- >This is probably a FAQ, but I can't find a decent answer anywhere.
- >
- >What is the correct way to detect user breaks (CTRL-C,D,E,F) in machine
- >code? I noticed that they are implemented as signals (12..15 as I remember)
-
- You use a Signal() call to check SIGBREAKF_CTRL_C/D/E/F to check them or
- better CheckSignal() in >=V36.
-
- >but according to my documentation those are reserved for system use.
-
- They have a system defined meaning. You are allowed to check for them.
-
- >Is it correct to use SetException() on them?
-
- It's ok to use SetException() on them but maybe it's easier for you to use
- CheckSignal() in your program.
-
- > - Marcel van Kervinck
-
- --
- Heinz Wrobel, Edotronik GmbH (ECG018)
- FAX +49 89 850 51 25 / TEL +49 89 850 25 20 (HOME!&VOICE, sometimes...)
- Path: cbmehq!cbmger!edohwg!heinz@cbmvax.commodore.com
- "It's good to have a mouse, it's faster if you can do without one..."
- "He who doesn't develop with an A2024 doesn't know about font independent
- user interfaces..."
-