Re: -mdoc: how to handle surrounding types?

On Thu, 8 Feb 2024, Mouse wrote: I'm writing a manpage for a library and want to describe a function which returns a pointer to a function. Specifically, it takes a handler of type void (*)(const char *, int) and returns the previous handler. If we call it foo, then: extern void (*foo(void (*

-mdoc: how to handle surrounding types?

I'm writing a manpage for a library and want to describe a function which returns a pointer to a function. Specifically, it takes a handler of type void (*)(const char *, int) and returns the previous handler. If we call it foo, then: extern void (*foo(void (*)(const char *, int)))(const char *,

Ping: [PATCH] inttypes.h: strtoi(), strtou(): Prefer reporting ERANGE over ENOTSUP

Hi Guillem! On Wed, Jan 24, 2024 at 07:16:23PM +0100, Alejandro Colomar wrote: > If both ERANGE and ENOTSUP conditions happen, ENOTSUP can be tested > secondarily as `*end != '\0'`. However, there's no secondary mechanism > to test ERANGE. Thus, it is important to report ERANGE, and let the > us