From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Ape: Fix assert warnings.
Date: Tue, 18 Jun 2019 13:57:01 +0200 [thread overview]
Message-ID: <13569CF21A85FF24FFC35A110A539EAB@felloff.net> (raw)
In-Reply-To: 20190617123612.046f000c6b470aa989c94fac@eigenstate.org
i remember assert was changed because there was some
usecase where assert() was used in a expression.
changeset: 6435:c4a6eb67bc9a
user: mischief <mischief@offblast.org>
date: Mon Apr 02 21:44:21 2018 -0700
summary: ape: improve assert macro
maybe mischief can clear up the detalis.
maybe the warning should be fixed in the compiler?
--
cinap
next reply other threads:[~2019-06-18 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 11:57 cinap_lenrek [this message]
2019-06-18 14:26 cinap_lenrek
2019-06-18 14:35 cinap_lenrek
2019-06-18 16:36 ` Ori Bernstein
2019-06-18 14:37 cinap_lenrek
2019-06-18 16:46 cinap_lenrek
2019-06-18 20:37 ` Ori Bernstein
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=13569CF21A85FF24FFC35A110A539EAB@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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 NNTP newsgroup(s).