Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
9 changed files
with
1,107 additions
and
1,098 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
root = true | ||
|
||
[*.{c,h,d,di,dd}] | ||
end_of_line = crlf | ||
insert_final_newline = true | ||
indent_style = tab | ||
indent_size = 4 | ||
trim_trailing_whitespace = true | ||
charset = utf-8 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,50 +1,50 @@ | ||
Ddoc | ||
|
||
$(P DMD comes with an option to instrument an executable for coverage analysis | ||
during its execution. You can enable it on the project configuration page "Code Generation".) | ||
|
||
$(IMG_CENTER images/prop_codegen.png) | ||
|
||
$(P With code coverage enabled the executable will record | ||
the source code lines that have been executed and will mark the lines that have | ||
code generated but are never executed. This information is written into files named as the | ||
source files but with extension ".lst".) | ||
|
||
<table><tr><td valign="top" width="70%"> | ||
$(P If you enable option "Colorize Coverage" in | ||
the Visual D colorizer settings (reachable through the "Open Language Options..." entry | ||
in the Visual D menu), these lines will be highlighted in the editor. The highlighting will not show | ||
up unless the lst-file is newer than the source file as it will probably be out of sync | ||
otherwise. | ||
) | ||
|
||
</td><td width="30%"> | ||
$(IMG_CENTER images/coverage_forever.png) | ||
</td></tr></table> | ||
|
||
$(P If you start editing the source file Visual D will try to keep coverage information in sync. | ||
If you want to get rid of the coverage coloring, just resave the source file. | ||
Visual D will assume the coverage is invalid then and stop displaying it. | ||
) | ||
|
||
<table><tr><td valign="top" width="70%"> | ||
$(P Enabling "Show coverage margin" on the same options page will add a column | ||
to the editor window that displays the exact coverage counters for each line.) | ||
|
||
$(P The very first line contains the percentage of covered source lines with generated | ||
code in the module.) | ||
|
||
$(P [Visual Studio 2008 displays the coverage margin as an overlay on the right side | ||
of the editor window.]) | ||
|
||
</td><td width="30%"> | ||
$(IMG_CENTER images/coveragemargin_forever.png) | ||
</td></tr></table> | ||
|
||
This option can be combined with the "Compile and Run" command to easily test | ||
the code coverage of unittests within a module. See $(LINK2 News36.html, Unit testing and code coverage) | ||
for an example. | ||
|
||
Macros: | ||
TITLE=Code Coverage | ||
|
||
Ddoc | ||
$(P DMD comes with an option to instrument an executable for coverage analysis | ||
during its execution. You can enable it on the project configuration page "Code Generation".) | ||
$(IMG_CENTER images/prop_codegen.png) | ||
$(P With code coverage enabled the executable will record | ||
the source code lines that have been executed and will mark the lines that have | ||
code generated but are never executed. This information is written into files named as the | ||
source files but with extension ".lst".) | ||
<table><tr><td valign="top" width="70%"> | ||
$(P If you enable option "Colorize Coverage" in | ||
the Visual D colorizer settings (reachable through the "Open Language Options..." entry | ||
in the Visual D menu), these lines will be highlighted in the editor. The highlighting will not show | ||
up unless the lst-file is newer than the source file as it will probably be out of sync | ||
otherwise. | ||
) | ||
</td><td width="30%"> | ||
$(IMG_CENTER images/coverage_forever.png) | ||
</td></tr></table> | ||
$(P If you start editing the source file Visual D will try to keep coverage information in sync. | ||
If you want to get rid of the coverage coloring, just resave the source file. | ||
Visual D will assume the coverage is invalid then and stop displaying it. | ||
) | ||
<table><tr><td valign="top" width="70%"> | ||
$(P Enabling "Show coverage margin" on the same options page will add a column | ||
to the editor window that displays the exact coverage counters for each line.) | ||
$(P The very first line contains the percentage of covered source lines with generated | ||
code in the module.) | ||
$(P [Visual Studio 2008 displays the coverage margin as an overlay on the right side | ||
of the editor window.]) | ||
</td><td width="30%"> | ||
$(IMG_CENTER images/coveragemargin_forever.png) | ||
</td></tr></table> | ||
This option can be combined with the "Compile and Run" command to easily test | ||
the code coverage of unittests within a module. See $(LINK2 News36.html, Unit testing and code coverage) | ||
for an example. | ||
Macros: | ||
TITLE=Code Coverage | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,3 @@ | ||
// missing from VS12 SDK? | ||
|
||
module sdk.port.sharedvenusids; | ||
// missing from VS12 SDK? | ||
|
||
module sdk.port.sharedvenusids; |
Oops, something went wrong.