Re: Do D need a popular framework? like ruby's rails? or java 's ssh?
On Thursday, 4 February 2016 at 15:37:21 UTC, sigod wrote: On Tuesday, 19 January 2016 at 13:22:48 UTC, beck wrote: Do D need a popular framework? in china ,a little peopel use dlang. i just use it do some simple work for myself. yet,i have learn d for a week .. i ask so many friends ,they don't use D at all.we use golang more than dlang. Oh, I thought I'll see here a suggestion to port some popular and useful libraries/frameworks from other languages... Seriously, it might be an interesting idea. I want to port some parts of PHP Symfony: https://github.com/caraus-ecms/caraus I've just started and it is kind of "learning project", I haven't written anything in D before. On the other hand I'm writting a personal project (kind of CMS/Blog) and this Symfony port is the base for this project. Don't know yet if I'll open source everything later.
Re: IDE - Coedit 2 rc1
On Monday, 8 February 2016 at 07:05:15 UTC, Suliman wrote: On Sunday, 7 February 2016 at 13:18:44 UTC, Basile Burg wrote: See https://github.com/BBasile/Coedit/releases/tag/2_rc1 Cool! Thanks! But do you have any plans to reimplement it from Pascal to D No.
Re: IDE - Coedit 2 rc1
On Monday, 8 February 2016 at 07:25:49 UTC, Dominikus Dittes Scherkl wrote: On Monday, 8 February 2016 at 07:05:15 UTC, Suliman wrote: Cool! Thanks! But do you have any plans to reimplement it from Pascal to В to get it's more native... B? What is B? https://en.wikipedia.org/wiki/B_(programming_language) but obviously he meant D.
unit-threaded v0.5.7 - advanced multi-threaded unit testing library
What's new:
Built-in unittest blocks can now have a name with just a string
UDA:
@("test that does stuff") unittest {... }
Why is this important? If you just want to run unit tests in
threads and have them named, you don't need to import
unit_threaded in your source code anymore. I'm going to build on
this later with a tool to make it so that existing codebases can
benefit from unit_threaded without using it directly.
Value-parametrized tests
Have you ever written a test that looks like this?
unittest {
foreach(v; [...]) {
//test code
}
}
I have, and when it fails you have no idea which of the values
caused the failure. Now, you can do this:
@(42, 2, 3)
void testValues(int i) {
(i % 2 == 0).shouldBeTrue;
}
testValues will be run once for each value UDA with the same type
in its declaration (in this case, int). Each run will be
considered a different test and reported as such with the value
that was used. In the above case, the output will contain this:
tests.pass.attributes.testValues.42:
tests.pass.attributes.testValues.2:
tests.pass.attributes.testValues.3:
tests/pass/attributes.d:76 - Expected: true
tests/pass/attributes.d:76 - Got: false
Test tests.pass.attributes.testValues.3 failed.
Enjoy!
Atila
