15 | | Doxygen generates [http://smartmontools.sourceforge.net/doxygen/ documentation pages] automatically by ''reading'' the sourcecode. |
16 | | We use the following styles for inline comments: |
| 15 | Doxygen generates our [http://smartmontools.sourceforge.net/doxygen/ sourcecode documentation pages] |
| 16 | automatically by ''reading'' the sourcecode. If you set a block with C++ comment lines, |
| 17 | where each line starts with an additional slash, the text will be shown in the doxygen generated docs. |
| 18 | Note that a blank line ends a documentation block. You may add two blocks, a first one with a brief description |
| 19 | and a second with an extended description for a class, struct or function. |
| 25 | class sat_device |
| 26 | }}} |
| 27 | |
| 28 | Use ''in line'' comment style to add explanation on defines and variables. |
| 29 | A comment starting with three slashes, will appear in doxygen. |
| 30 | Comments that start with only two slashes, will be invisible there. |
| 31 | |
| 32 | {{{ |
| 33 | // ATA ONLY |
| 34 | bool sct_erc_set; // set SCT ERC to: |
| 35 | unsigned short sct_erc_readtime; // ERC read time (deciseconds) |
| 36 | unsigned short sct_erc_writetime; // ERC write time (deciseconds) |
| 37 | |
| 38 | unsigned char curr_pending_id; // ID of current pending sector count, 0 if none |
| 39 | unsigned char offl_pending_id; // ID of offline uncorrectable sector count, 0 if none |
| 40 | }}} |