> '.cu' doesn't do what any sane person > would expect it to do for PostScript output
I understand the need for backwards compatibility, but I more and more find myself wishing groff had a global option to choose between "follow historical usage" and "be sane." For someone in 2014 writing a new groff document, there is zero advantage to, for example, having calculations treat addition and multiplication as the same precedence, or any of a dozen other little pitfalls that exist solely for compatibility with a 1970s back end.
