On Wed, Jun 4, 2014 at 12:42 PM, Jannis Froese
s9jaf...@stud.uni-saarland.de wrote:
I think most concerns about the current use of asserts would be resolved if
the currently used asserts would be changed to a nicer definition which is
independent of NDEBUG, and a second class of debugging
Hi Ron,
FYI your mail is being spamfoldered due to Yahoo's DMARC policy and the
brokenness of the SF.net mailing list software. I would not expect to get
replies reliably whilst this is the case. I think we should move away from
SF.net for hosting mailing lists personally, because it's this list
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
On Wed, Jun 4, 2014 at 12:42 PM, Jannis Froese
s9jaf...@stud.uni-saarland.de wrote:
I think most concerns about the current use of asserts would be resolved
if the currently used asserts would be changed to a nicer definition which
is independent of NDEBUG, and a second class of debugging
Message: 2
Date: Wed, 4 Jun 2014 08:15:08 -0400
From: Jeff Garzik jgar...@bitpay.com
Subject: Re: [Bitcoin-development] # error Bitcoin cannot
be compiled
without assertions. NOT
To: Mike Hearn m...@plan99.net
Cc: bitcoin
5 matches
Mail list logo
