On Tue, 17 Mar 2009 18:54:23 -0400, Mason Green wrote:
Brian wrote:
I don't know how different Blaze 2.0 is from the version i had, but
I'll take a look when I get a chance and see if I can be of any help.
I'm using Box2D for the time being because there were still GC issues,
but I'm very
Brian wrote:
That sounds good. I'll see if I can do a nice 3 way comparison between
box2d and blaze 1.0/2.0 and also see if I can find any speedups. I don't
have much time to spare unfortunately.
Great, if you can find the spare time it would be greatly appreciated
:-) I think a comparison
Christopher Wright:
Having other testing frameworks/tools for D is good. There are many kinds of
testing, and the built-in one isn't supposed to implement them all.
Regarding the issues of unit testing with unittest{}, I think the built-in
unittesting has to be improved, to removed some of
On Thu, 19 Mar 2009 11:34:52 -0400, bearophile
bearophileh...@lycos.com wrote:
Christopher Wright:
Having other testing frameworks/tools for D is good. There are many kinds of
testing, and the built-in one isn't supposed to implement them all.
Regarding the issues of unit testing with
On Thu, 19 Mar 2009 18:26:32 +, Gide Nwawudu g...@btinternet.com
wrote:
On Thu, 19 Mar 2009 11:34:52 -0400, bearophile
bearophileh...@lycos.com wrote:
Christopher Wright:
Having other testing frameworks/tools for D is good. There are many kinds of
testing, and the built-in one isn't
bearophile wrote:
Christopher Wright:
Having other testing frameworks/tools for D is good. There are many kinds of
testing, and the built-in one isn't supposed to implement them all.
Regarding the issues of unit testing with unittest{}, I think the built-in
unittesting has to be improved, to
bearophile wrote:
For me it's often better to keep tests very close to the things they test. It
helps me spot and fix bugs faster, to avoid jumping across files, and when I
quickly move a block of code (function, class, template, etc) when I reorganize
the code it is less likely for me to
Christopher Wright dhase...@gmail.com wrote in message
news:gpuibc$1nr...@digitalmars.com...
bearophile wrote:
What's the advantage of:
expect(foo(5), equals(3) | greaterThan(5));
Compared to:
expect(foo(5) == 3 | foo(5) 5);
What error message should that give?
The former gives:
Christopher Wright wrote:
bearophile wrote:
What's the advantage of:
expect(foo(5), equals(3) | greaterThan(5));
Compared to:
expect(foo(5) == 3 | foo(5) 5);
What error message should that give?
The former gives:
Expected: equal to 3 or greater than 5
But was: whatever value foo(5)
