[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] [PATCH 0/2] Fix #t being "not always-true"

From: Peter Bex
Subject: Re: [Chicken-hackers] [PATCH 0/2] Fix #t being "not always-true"
Date: Sun, 24 May 2015 16:23:45 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Sun, Apr 19, 2015 at 03:03:04PM +1200, Evan Hanson wrote:
> Hi hackers,
> This morning I tried to figure out why treating #t as `always-true` in
> the scrutinizer breaks bootstrapping (after ddb2b63 and noted by Peter
> in <address@hidden>), and it turns out it's
> simply because we're (mis)using the "-local" flag when building the
> system's compiler objects (so, compiler.c, batch-driver.c, etc.).

I see you're also removing "true" from the list of things considered to be
NOT always-true, like I mentioned in my earlier mail
(<address@hidden>).  But your patch doesn't
include the testcase I added in that mail.  Do you believe the test is
not useful, or wrong?


Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]