[Issue 5091] main runs after unittests

https://issues.dlang.org/show_bug.cgi?id=5091 --- Comment #14 from Andrej Mitrovic --- These days I just use: - import std.stdio; version (unittest) void main() { writeln("Tests finished"); } else: void main ( string[] args ) { // .. } - It doesn't

[Issue 5091] main runs after unittests

https://issues.dlang.org/show_bug.cgi?id=5091 Andrei Alexandrescu changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 5091] main runs after unittests

https://issues.dlang.org/show_bug.cgi?id=5091 Andrei Alexandrescu and...@erdani.com changed: What|Removed |Added Version|D1 D2 |D2 --

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 Martin Nowak c...@dawg.eu changed: What|Removed |Added CC||c...@dawg.eu --- Comment

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 --- Comment #8 from Andrej Mitrovic andrej.mitrov...@gmail.com 2013-03-13 12:17:24 PDT --- (In reply to comment #7) It's a little hacky though, because returning false is interpreted as failed tests. Yeah, I've realized that after posting.

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 --- Comment #9 from Andrej Mitrovic andrej.mitrov...@gmail.com 2013-03-13 16:27:36 PDT --- (In reply to comment #7) It's a little hacky though, because returning false is interpreted as failed tests. Perhaps we could change ModuleUnitTester

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 --- Comment #10 from Martin Nowak c...@dawg.eu 2013-03-13 20:42:41 PDT --- This always confused me a little because the documentation is inconsistent. http://dlang.org/phobos/core_runtime.html#moduleUnitTester

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 --- Comment #11 from Andrej Mitrovic andrej.mitrov...@gmail.com 2013-03-13 20:49:45 PDT --- (In reply to comment #10) This always confused me a little because the documentation is inconsistent.

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 --- Comment #12 from Martin Nowak c...@dawg.eu 2013-03-13 21:58:50 PDT --- (In reply to comment #11) Speaking of which I just noticed that `runAll` doesn't wrap `runModuleUnitTests()` in a try/catch. That seems like a bug to me. It does

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 Andrej Mitrovic andrej.mitrov...@gmail.com changed: What|Removed |Added CC|

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 --- Comment #5 from Peter Alexander peter.alexander...@gmail.com 2010-10-22 00:43:56 PDT --- (In reply to comment #4) I have not once wanted to run both the full application and the unittests at the same time. when I want to run the

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 Peter Alexander peter.alexander...@gmail.com changed: What|Removed |Added CC|

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 --- Comment #2 from Peter Alexander peter.alexander...@gmail.com 2010-10-21 01:11:22 PDT --- Even if you don't buy that argument, consider this: with the current unittest, you only have to add a few lines of code to turn it off (as you

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 bearophile_h...@eml.cc changed: What|Removed |Added CC||bearophile_h...@eml.cc ---

[Issue 5091] main runs after unittests

http://d.puremagic.com/issues/show_bug.cgi?id=5091 --- Comment #4 from Simen Kjaeraas simen.kja...@gmail.com 2010-10-21 10:32:36 PDT --- (In reply to comment #1) (In reply to comment #0) When compiling a program with dmd -unittest, after the unittests are run, main() is called. This is