On Friday, 6 June 2014 at 14:21:38 UTC, Rene Zwanenburg wrote:
Please try compiling with -g (generate debug info). The magic
numbers should turn into a stack trace, so you know where the
assert is triggered.
This helped quite a bit. The program was hitting an assert(0)
which I had ruled out
Hello all, I have a program which works perfectly when compiled
without -release:
parser a implies b equivalent not b implies not a
Input: ((a implies b) equivalent ((not b) implies (not a)))
CNF: (not a) or b) or (not b)) and (((not a) or b) or a)) and
(((b or (not a
)) or a) and ((b or
On Fri, 06 Jun 2014 10:10:24 +
Mikko Aarnos via Digitalmars-d-learn
digitalmars-d-learn@puremagic.com wrote:
Hello all, I have a program which works perfectly when compiled
without -release:
parser a implies b equivalent not b implies not a
Input: ((a implies b) equivalent ((not b)
On Friday, 6 June 2014 at 10:10:25 UTC, Mikko Aarnos wrote:
Hello all, I have a program which works perfectly when compiled
without -release:
parser a implies b equivalent not b implies not a
Input: ((a implies b) equivalent ((not b) implies (not a)))
CNF: (not a) or b) or (not b)) and
