Re: -mdoc: how to handle surrounding types?

2024-02-09 Thread Rhialto
On Fri 09 Feb 2024 at 08:37:31 -0500, Mouse wrote: > > \X/ There is no AI. There is just someone else's work. --I. Rose > > Becoming less true, to the extent that weak AI qualifies. > > Reminds me of "Don't say `the cloud'. Say `someone else's computer'." That's exactly what it refers

Re: -mdoc: how to handle surrounding types?

2024-02-09 Thread Mouse
>> I'm writing a manpage for a library and want to describe a function >> which returns a pointer to a function. >> extern void (*foo(void (*)(const char *, int)))(const char *, int); [RVP] > After a bit of fiddling with signal.3: Doh! Of course signal(3) is an example. > +.ds cm \f[R],\f[] >

Re: -mdoc: how to handle surrounding types?

2024-02-09 Thread Rhialto
On Thu 08 Feb 2024 at 23:59:24 -0500, Mouse wrote: > I'm writing a manpage for a library and want to describe a function > which returns a pointer to a function. signal(3) has a similar case, right? And it spells out the type in full. So you could look there for inspiration. However I would prefe