Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.c    |    Meh, in C you gotta define EVERYTHING    |    243,242 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 241,855 of 243,242    |
|    Michael Sanders to Lew Pitcher    |
|    Re: SIG_DFL    |
|    08 Nov 25 19:33:02    |
      From: porkchop@invalid.foo              On Sat, 8 Nov 2025 19:28:20 -0000 (UTC), Lew Pitcher wrote:              > On Sat, 08 Nov 2025 19:01:00 +0000, Michael Sanders wrote:       >       >> One of many newbie questions from me... Cant find the info I'm looking for.       >>       >> If SIG_IGN is an acronym for signal ignore, then what does DFL mean?       >> I've know (well I presume) it restores default behavior, but the acronym?       >       > From the C11 draft standard (yes, I know, but that's the most current I have)       >       > 7.14.1.1 The signal function       > 2. ... If the value of func is SIG_DFL, default handling for that       > signal will occur.       >       > Neither the C standard, nor the Posix standards or Unix manuals before that,       > seem to specify exactly _why_ SIG_DFL is named that way. Presumably because       > other abbreviations would somehow conflict or possibly be confused with       > existing nomenclature (SIGUSR1 and SIGUSR2, for instance, are user-DEFined       > signals, and SIG_DEF might confuse someone who isn't entirely familiar with       > the nomenclature), or because (like many abbreviations in Unix, "DeFauLt"       > made more sense to someone.              Thanks again Lew. I'm running with: [D]e[F]ault [L]evel in my // comments.              --       :wq       Mike Sanders              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca