Re:F() vs. F(void) in C vs. C++
by saagarjha on Monday May 13, 2019 @01:48AM
(#19896669)
Yes, I know this: I'm relying POSIX's guarantees and not what ISO C mandates (also truth be told I usually do this in Objective-C, but that doesn't actually change anything significantly). Unfortunately I get a function pointer and need forward essentially anything, so I'm not going to have any sort of type safety at all…
[ Parent
| on HN ]
What guarantees does POSIX make about calling functions that are not in ISO C? I'm curious.
POSIX generaly has very little to say about C matters; for the most part it defers to ISO C by normative reference.
Off the top of my head, because POSIX specifies dlopen and dlsym, that pretty much requires function pointers have to have a common representation convertible between void * and back.