[m-rev.] for review: generate warnings only when generating code

Zoltan Somogyi zoltan.somogyi at runbox.com
Tue Apr 25 11:02:09 AEST 2017


For review of the concept by anyone. (The implementation
is straightforward.)

I wrote this because the warnings you get when the compiler
is generating interface or optimization files are in a sense
too early. One, they get put on standard output, not in the
module's .err file, and two, if halt-at-warn is specified, they stop
an invocation of make after the first module that has warnings.

Zoltan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Log.nowarn
Type: application/octet-stream
Size: 142 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20170425/8c934e1c/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DIFF.nowarn
Type: application/octet-stream
Size: 2628 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20170425/8c934e1c/attachment-0001.obj>


More information about the reviews mailing list