[m-dev.] --inform-suboptimal-packing and error outputs

Julien Fischer jfischer at opturion.com
Mon Jun 1 00:29:07 AEST 2020

On Sun, 31 May 2020, Zoltan Somogyi wrote:

> However, before we can switch to a regime where all problems detected
> at interface-file-generation time are reported to the user at that time,
> we have to decide where any such messages (whether errors, warnings,
> or informational) should go. Should they go to stdout/stderr, as now,
> or to module.err, or to a new file such as module.int_err/.int3_err?
> None of those seem particularly appealing, though I can think of fewer
> negatives for module.err than for the others.

I vote for module.err.  For mmc --make, up to
--output-compile-error-lines should go to standard error as now.


More information about the developers mailing list