On Mon, May 16, 2016 at 10:48 AM, Tony Harminc <[email protected]> wrote:
> On 16 May 2016 at 11:29, Paul Gilmartin > <[email protected]> wrote: > > In circumvention, AIX introduced a nonstandard signal, SIGDANGER, > > thrown when backing storage was (FSVO) nearly exhausted. > > OT, but are signals "thrown"? I know that in C++ and Java, exceptions > are objects and are "thrown" (and perhaps "caught"), where in PL/I and > some other languages they are states and are "raised". But signals...? > [Just to compund things, PL/I (and REXX) has a SIGNAL verb that raises > an exception.] > Yes, signals are "thrown". But the program doesn't do the throwing. The OS "throws" the signal asynchronously, which the program must "catch" via something like a sigaction(). In many cases, the language start up routines or the OS will set up a default signal action, usually to simply ignore the signal. Unless it is a critical error such as SIGSEGV (S0C4 type abend in z/OS). > > Tony H. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- The unfacts, did we have them, are too imprecisely few to warrant our certitude. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
