Re: On code quality, C, and C++ (was: Proposed: QS/QE macros for quotation in man(7))

[onf]

On Fri Dec 20, 2024 at 10:54 PM CET, onf wrote:
> Let's say I want to check out the need method of curdiv.
> To do that, I first need to figure out what object it is.
> Searching for curdiv eventually reveals it being declared
> in div.cpp as type `diversion`. Searching for diversion::need
> then finally reveals the desired method. If I chose something
> other than curdiv, I would have to figure out which header
> files declares it to figure out where to search for its
> definition.

s/its/the method's/

> I'm not saying it's an insurmountable obstacle by any means,
> but it's annoying. The fact that groff's code style doesn't make
> function- I mean method declarations easily greppable doesn't
> help, either. What I'm trying to get at is that in a good C code
> base, if I wanted to locate the definition of function div_need,
> I would simply run:

s/declarations/definitions/