Re:Show HN: Cdecl-dump - represent C declarations visually
by saagarjha on Sunday December 07, 2025 @11:18PM
(#46188242)
Of course, the correct way to use a function pointer is to call it.
[ Parent
| on HN ]
Re:Show HN: Cdecl-dump - represent C declarations visually
by nitrix on Sunday December 07, 2025 @11:19PM
(#46188249)
Yes, the () operator dereference function pointers automatically for you for convenience. There's also the surprise that you can infinitely dereference function pointers as they just yield you more function pointers.
Re:Show HN: Cdecl-dump - represent C declarations visually
by korianders on Monday December 08, 2025 @05:25AM
(#46190662)
One baffling thing I see people do with typedefing function pointers is insisting on adding in the pointer part in the typedef which just complicates and hides things.
If you want to typedef a function pointer, make a completely ordinary function declaration, then slap 'typedef' at the beginning, done. This does require you to do "foo_func *f" instead of "foo_func f" when declaring variables, but that is just clearer imo.
typedef int foo_func(int); // nice
typedef int (*foo_func)(int); // why?
Re:Show HN: Cdecl-dump - represent C declarations visually
by cryptonector on Monday December 08, 2025 @12:57PM
(#46195456)
Why do you need the `*` to be part of every variable/member declaration?