Making D Lang More easy.
Walter Bright
newshound2 at digitalmars.com
Wed May 11 11:23:11 PDT 2011
On 5/11/2011 6:41 AM, Matthew Ong wrote:
> 5) import std.stdio; // The imports seems to be more complex to use
> than java's import. There should be a tool to help resolved this and
> also makes the order of importing of not important like in java.
Not sure what you mean by more complex than Java. The order of imports in D is
not important.
> 6) Is there some build in source code checking command like:
> govet
> http://golang.org/cmd/
No.
>
> 7) How about unit test, is there a library like junit or cppunit
> is there something similar that can allow code to be profile,
> tested and validated?
D has builtin unittest support with the -unittest switch:
http://www.digitalmars.com/d/2.0/unittest.html
a builtin profiler enabled with the -profile switch:
http://www.digitalmars.com/ctg/trace.html
and builtin code coverage analysis with the -cov switch:
http://www.digitalmars.com/d/2.0/code_coverage.html
> May I also ask, does the compiler and linker highlight the unused
> import to the user so that they can be removed from source code.
This was discussed and we decided it was not a good idea for various reasons.
More information about the Digitalmars-d
mailing list