From: Per Bothner <per@bothner.com>
To: Duncan Mak <duncanmak@gmail.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Show all warnings and errors
Date: Tue, 01 Jan 2019 21:42:00 -0000 [thread overview]
Message-ID: <7ebffea4-cd41-20be-d4b4-8378159a9439@bothner.com> (raw)
In-Reply-To: <CABgWrqpKPB4UOfSMsZQOSNkdYWWb3SykexUhk2JMBa=OeCsU7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
On 1/1/19 1:30 PM, Duncan Mak wrote:
> It looks like this:
> https://gist.github.com/duncanmak/38f451c9f26ba0000be38d0bd304313b#file-more-changes
Ah - as I suspected, I missed a call to Compilation.maxERrors.
Try the attached patch.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
[-- Attachment #2: ModExp.patch --]
[-- Type: text/x-patch, Size: 613 bytes --]
diff --git a/gnu/expr/ModuleExp.java b/gnu/expr/ModuleExp.java
index f2e3c2ec0..f017a72b8 100644
--- a/gnu/expr/ModuleExp.java
+++ b/gnu/expr/ModuleExp.java
@@ -230,7 +230,8 @@ public class ModuleExp extends LambdaExp
comp.process(Compilation.RESOLVED);
comp.getMinfo().loadByStages(Compilation.WALKED);
- if (msg != null ? messages.checkErrors(msg, 20) : messages.seenErrors())
+ if (msg != null ? messages.checkErrors(msg, Compilation.maxErrors())
+ : messages.seenErrors())
return null;
if (! comp.mustCompile) {
next prev parent reply other threads:[~2019-01-01 21:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 23:18 Duncan Mak
2019-01-01 2:12 ` Per Bothner
2019-01-01 2:33 ` Duncan Mak
2019-01-01 2:42 ` Per Bothner
2019-01-01 20:47 ` Duncan Mak
2019-01-01 20:58 ` Per Bothner
2019-01-01 21:16 ` Duncan Mak
2019-01-01 21:24 ` Per Bothner
2019-01-01 21:31 ` Duncan Mak
2019-01-01 21:42 ` Per Bothner [this message]
2019-01-01 22:08 ` Duncan Mak
2022-09-18 3:03 ` Duncan Mak
2022-09-18 19:11 ` Per Bothner
2022-09-18 22:06 ` Duncan Mak
2022-09-19 10:48 ` Per Bothner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ebffea4-cd41-20be-d4b4-8378159a9439@bothner.com \
--to=per@bothner.com \
--cc=duncanmak@gmail.com \
--cc=kawa@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).