![]() |
![]() |
![]() |
![]() 17 |
|||||||||||
|
||||||||||||||
The merge command is initiated with the following call: |
||||||||||||||
covered merge [<options>] <existing_CDD> <CDD_to_merge>+ |
||||||||||||||
The existing_CDD specifier relates to any existing CDD. If the -o option is not specified (see below for details), this file will be replaced with the merged CDD created by the merge. This is important to remember since merging is an irreversible operation (apart from generating a brand-new CDD from the design and dumpfile using the score command). |
||||||||||||||
The CDD_to_merge specifier relates to any existing CDD that is not the existing_CDD. Though it is not illegal to merge the same CDD to itself, the result is the same as the original CDD. Note that all files treated as CDD_to_merge are guaranteed not to be modified by the merge command. These files are only read by Covered and then merged into the information contained in the existing_CDD. |
||||||||||||||
The following table lists the options available for the merge command. |
||||||||||||||
|
||||||||||||||
[ 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 ] License: GPL This Manual was originally created with ManStyle. |