Follow-up Comment #8, bug #62776 (project groff):
[comment #6 comment #6:]
> Also I think the technique you describe, which I have not seen in the wild,
might be too clever by half. Better to say in English in a comment, "This
macro is intended to cause no breaks.", no?
I tend to prefer actual code than comments. Comments can get out of date.
Code not (or well, it does, but you would notice more easily).
About the warning, I think I prefer having it. Disabling a warning if you
don't care is easy. But if the warning is not there, you can't add it :)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62776>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
