From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Ws8BR-0005uO-1K for bitcoin-development@lists.sourceforge.net; Wed, 04 Jun 2014 10:12:37 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.175 as permitted sender) client-ip=209.85.223.175; envelope-from=laanwj@gmail.com; helo=mail-ie0-f175.google.com; Received: from mail-ie0-f175.google.com ([209.85.223.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Ws8BP-0001lF-9C for bitcoin-development@lists.sourceforge.net; Wed, 04 Jun 2014 10:12:36 +0000 Received: by mail-ie0-f175.google.com with SMTP id y20so6758318ier.6 for ; Wed, 04 Jun 2014 03:12:29 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.92.42 with SMTP id cj10mr5474722igb.34.1401876749289; Wed, 04 Jun 2014 03:12:29 -0700 (PDT) Received: by 10.64.60.195 with HTTP; Wed, 4 Jun 2014 03:12:29 -0700 (PDT) In-Reply-To: References: <1401822421.27942.YahooMailNeo@web124505.mail.ne1.yahoo.com> Date: Wed, 4 Jun 2014 12:12:29 +0200 Message-ID: From: Wladimir To: Mike Hearn Content-Type: multipart/alternative; boundary=047d7b10d0b5a9133b04faffddf3 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Ws8BP-0001lF-9C Cc: "bitcoin-development@lists.sourceforge.net" , Ron Subject: Re: [Bitcoin-development] # error "Bitcoin cannot be compiled without assertions." <<< List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 10:12:37 -0000 --047d7b10d0b5a9133b04faffddf3 Content-Type: text/plain; charset=UTF-8 > > > assert() should have *no* side effects, that is the problem. >> > I'm pretty sure that all the side effects of assertions have been removed before 0.9.0. However, the assertion checks are extremely important to the proper sanity of the client and network, so IMHO it's fair to still require building with them enabled. Wladimir --047d7b10d0b5a9133b04faffddf3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

assert() should have = no side effects, that is the problem.

I'm pretty sure that all the side effects of assertions have been = removed before 0.9.0.

However, the assertion checks are e= xtremely important to the proper sanity of the client and network, so IMHO = it's fair to still require building with them enabled.

Wladimir


--047d7b10d0b5a9133b04faffddf3--