From: chris.m.thomasson.1@gmail.com   
      
   On 1/2/2026 1:52 PM, Kaz Kylheku wrote:   
   > On 2026-01-02, Michael Sanders  wrote:   
   >> On Fri, 2 Jan 2026 17:48:16 -0000 (UTC), Kaz Kylheku wrote:   
   >>   
   >>> On 2026-01-02, Michael Sanders  wrote:   
   >>>> B: because every function must have a return type   
   >>>>     *including function pointers*?   
   >>>   
   >>> What it is you think type is, in the context of C?   
   >>>   
   >>> Does type survive into run-time?   
   >>>   
   >>> If a function pointer is missing type information about return type, and   
   >>> that function pointer is needed for expressing a function call, where   
   >>> does the compiler get the type from?   
   >>   
   >> Its void that's throwing me Kaz. I'm not sure what to think when   
   >> it comes to void pointers.   
   >   
   > Because you teleported here from 1985.   
      
   [...]   
      
   One note, void* cannot hold a function pointer without getting undefined   
   or implementation-defined behavior.   
      
   typedef void (*generic_func_ptr)(void)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)