From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Show all warnings and errors
Date: Tue, 01 Jan 2019 21:31:00 -0000 [thread overview]
Message-ID: <CABgWrqpKPB4UOfSMsZQOSNkdYWWb3SykexUhk2JMBa=OeCsU7A@mail.gmail.com> (raw)
In-Reply-To: <008aca45-bf67-e8db-54dc-76930b6682c8@bothner.com>
It looks like this:
https://gist.github.com/duncanmak/38f451c9f26ba0000be38d0bd304313b#file-more-changes
My patch looks like this:
https://gist.github.com/duncanmak/38f451c9f26ba0000be38d0bd304313b#file-sourcemessages-patch
On Tue, Jan 1, 2019 at 4:24 PM Per Bothner <per@bothner.com> wrote:
>
> On 1/1/19 1:15 PM, Duncan Mak wrote:
> > Hmm, my test runner is just an scm file that loads in a few files.
> >
> > It first loads in a file with some R7RS module definitions, and then I
> > load in some test files.
> >
> > Each of my test files look something like this:
> >
> > https://gist.github.com/duncanmak/03147dad1cd1697ca9ac3c2a7ee5ca8f
> >
> > I'm using SRFI 64 (ha! i just realized that's one of your SRFIs!),
> > maybe I need to write more code to explicitly instantiate a test
> > runner?
>
> Probably not. First try what I suggested in my previous message,
> to see where printAll is being called. That could be a place where
> we should (but don't) call Compilation.maxErrors().
>
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
--
Duncan.
next prev parent reply other threads:[~2019-01-01 21:31 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 [this message]
2019-01-01 21:42 ` Per Bothner
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='CABgWrqpKPB4UOfSMsZQOSNkdYWWb3SykexUhk2JMBa=OeCsU7A@mail.gmail.com' \
--to=duncanmak@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/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).