From: chris.m.thomasson.1@gmail.com   
      
   On 11/8/2025 12:14 PM, Kaz Kylheku wrote:   
   > On 2025-11-08, 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.   
   >   
   > It's not named SIGNAL_DEFAULT probably in order to harmonize with   
   > strpbrk, which is not named string_pointer_to_break.   
   >   
   > Programmers long ago loved creating "bumper stumpers" by removing   
   > vowels and some consontants too.   
      
   :^)   
      
   lol. For some reason it reminds me of the PPC instruction, EIEIO. ;^)   
      
      
   >   
   > I agree with them; I positively never want to write shit like   
   >   
   >    #include    
   >   
   > or work in any tech stack where that is the norm.   
   >   
   > The superfluous  "std" should have been omitted from ; other   
   > standard headers do not carry a reminder that they are standard, like   
   > ,  or .   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)