summaryrefslogtreecommitdiffstats
path: root/doc/commands.doc
blob: c569e6c196f6a6a05e6b98dac92eeb1879aa71a3 (plain)
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
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
/******************************************************************************
 *
 *
 *
 * Copyright (C) 1997-2015 by Dimitri van Heesch.
 *
 * Permission to use, copy, modify, and distribute this software and its
 * documentation under the terms of the GNU General Public License is hereby
 * granted. No representations are made about the suitability of this software
 * for any purpose. It is provided "as is" without express or implied warranty.
 * See the GNU General Public License for more details.
 *
 * Documents produced by Doxygen are derivative works derived from the
 * input used in their production; they are not affected by this license.
 *
 */
/*! \page commands Special Commands

\section cmd_intro Introduction

All commands in the documentation start with a backslash (<b>\\</b>) or an
at-sign (<b>\@</b>). If you prefer you can replace all commands starting with a
backslash below by their counterparts that start with an at-sign.

Some commands have one or more arguments.
Each argument has a certain range:
<ul>
<li>If \<sharp\> braces are used the argument is a single word.
<li>If (round) braces are used the argument extends until the end of the line
    on which the command was found.
<li>If {curly} braces are used the argument extends until the next paragraph.
    Paragraphs are delimited by a blank line or by a section indicator.
</ul>
If in addition to the above argument specifiers [square] brackets are used the argument is optional.

Here is an alphabetically sorted list of all commands with references to their
documentation:
\anchor showsecreflist
\secreflist
\refitem cmda \\a
\refitem cmdaddindex \\addindex
\refitem cmdaddtogroup \\addtogroup
\refitem cmdanchor \\anchor
\refitem cmdarg \\arg
\refitem cmdattention \\attention
\refitem cmdauthor \\author
\refitem cmdauthors \\authors
\refitem cmdb \\b
\refitem cmdbrief \\brief
\refitem cmdbug \\bug
\refitem cmdc \\c
\refitem cmdcallergraph \\callergraph
\refitem cmdcallgraph \\callgraph
\refitem cmdcategory \\category
\refitem cmdcite \\cite
\refitem cmdclass \\class
\refitem cmdcode \\code
\refitem cmdcond \\cond
\refitem cmdcopybrief \\copybrief
\refitem cmdcopydetails \\copydetails
\refitem cmdcopydoc \\copydoc
\refitem cmdcopyright \\copyright
\refitem cmddate \\date
\refitem cmddef \\def
\refitem cmddefgroup \\defgroup
\refitem cmddeprecated \\deprecated
\refitem cmddetails \\details
\refitem cmddiafile \\diafile
\refitem cmddir \\dir
\refitem cmddocbookonly \\docbookonly
\refitem cmddontinclude \\dontinclude
\refitem cmddot \\dot
\refitem cmddotfile \\dotfile
\refitem cmde \\e
\refitem cmdelse \\else
\refitem cmdelseif \\elseif
\refitem cmdem \\em
\refitem cmdemoji \\emoji
\refitem cmdendcode \\endcode
\refitem cmdendcond \\endcond
\refitem cmdenddocbookonly \\enddocbookonly
\refitem cmdenddot \\enddot
\refitem cmdendhtmlonly \\endhtmlonly
\refitem cmdendif \\endif
\refitem cmdendinternal \\endinternal
\refitem cmdendlatexonly \\endlatexonly
\refitem cmdendlink \\endlink
\refitem cmdendmanonly \\endmanonly
\refitem cmdendmsc \\endmsc
\refitem cmdendparblock \\endparblock
\refitem cmdendrtfonly \\endrtfonly
\refitem cmdendsecreflist \\endsecreflist
\refitem cmdendverbatim \\endverbatim
\refitem cmdenduml \\enduml
\refitem cmdendxmlonly \\endxmlonly
\refitem cmdenum \\enum
\refitem cmdexample \\example
\refitem cmdexception \\exception
\refitem cmdextends \\extends
\refitem cmdfdollar \\f\$
\refitem cmdfbropen \\f[
\refitem cmdfbrclose \\f]
\refitem cmdfcurlyopen \\f{
\refitem cmdfcurlyclose \\f}
\refitem cmdfile \\file
\refitem cmdfn \\fn
\refitem cmdheaderfile \\headerfile
\refitem cmdhidecallergraph \\hidecallergraph
\refitem cmdhidecallgraph \\hidecallgraph
\refitem cmdhiderefby \\hiderefby
\refitem cmdhiderefs \\hiderefs
\refitem cmdhideinitializer \\hideinitializer
\refitem cmdhtmlinclude \\htmlinclude
\refitem cmdhtmlonly \\htmlonly
\refitem cmdidlexcept \\idlexcept 
\refitem cmdif \\if
\refitem cmdifnot \\ifnot
\refitem cmdimage \\image
\refitem cmdimplements \\implements
\refitem cmdinclude \\include
\refitem cmdincludedoc \\includedoc
\refitem cmdincludelineno \\includelineno
\refitem cmdingroup \\ingroup
\refitem cmdinternal \\internal
\refitem cmdinvariant \\invariant
\refitem cmdinterface \\interface
\refitem cmdlatexinclude \\latexinclude
\refitem cmdlatexonly \\latexonly
\refitem cmdli \\li
\refitem cmdline \\line
\refitem cmdlink \\link
\refitem cmdmainpage \\mainpage
\refitem cmdmanonly \\manonly
\refitem cmdmemberof \\memberof
\refitem cmdmsc \\msc
\refitem cmdmscfile \\mscfile
\refitem cmdn \\n
\refitem cmdname \\name
\refitem cmdnamespace \\namespace
\refitem cmdnosubgrouping \\nosubgrouping
\refitem cmdnote \\note
\refitem cmdoverload \\overload
\refitem cmdp \\p
\refitem cmdpackage \\package
\refitem cmdpage \\page
\refitem cmdpar \\par
\refitem cmdparagraph \\paragraph
\refitem cmdparam \\param
\refitem cmdparblock \\parblock
\refitem cmdpost \\post
\refitem cmdpre \\pre
\refitem cmdprivate \\private
\refitem cmdprivatesection \\privatesection
\refitem cmdproperty \\property
\refitem cmdprotected \\protected
\refitem cmdprotectedsection \\protectedsection
\refitem cmdprotocol \\protocol
\refitem cmdpublic \\public
\refitem cmdpublicsection \\publicsection
\refitem cmdpure \\pure
\refitem cmdref \\ref
\refitem cmdrefitem \\refitem
\refitem cmdrelated \\related
\refitem cmdrelates \\relates
\refitem cmdrelatedalso \\relatedalso
\refitem cmdrelatesalso \\relatesalso
\refitem cmdremark \\remark
\refitem cmdremarks \\remarks
\refitem cmdresult \\result
\refitem cmdreturn \\return
\refitem cmdreturns \\returns
\refitem cmdretval \\retval
\refitem cmdrtfonly \\rtfonly
\refitem cmdsa \\sa
\refitem cmdsecreflist \\secreflist
\refitem cmdsection \\section
\refitem cmdsee \\see
\refitem cmdshort \\short
\refitem cmdshowinitializer \\showinitializer
\refitem cmdshowrefby \\showrefby
\refitem cmdshowrefs \\showrefs
\refitem cmdsince \\since
\refitem cmdskip \\skip
\refitem cmdskipline \\skipline
\refitem cmdsnippet \\snippet
\refitem cmdsnippetdoc \\snippetdoc
\refitem cmdsnippetlineno \\snippetlineno
\refitem cmdstartuml \\startuml
\refitem cmdstruct \\struct
\refitem cmdsubpage \\subpage
\refitem cmdsubsection \\subsection
\refitem cmdsubsubsection \\subsubsection
\refitem cmdtableofcontents \\tableofcontents
\refitem cmdtest \\test
\refitem cmdthrow \\throw
\refitem cmdthrows \\throws
\refitem cmdtodo \\todo
\refitem cmdtparam \\tparam
\refitem cmdtypedef \\typedef
\refitem cmdunion \\union
\refitem cmduntil \\until
\refitem cmdvar \\var
\refitem cmdverbatim \\verbatim
\refitem cmdverbinclude \\verbinclude
\refitem cmdversion \\version
\refitem cmdvhdlflow \\vhdlflow
\refitem cmdwarning \\warning
\refitem cmdweakgroup \\weakgroup
\refitem cmdxmlonly \\xmlonly
\refitem cmdxrefitem \\xrefitem
\refitem cmddollar \\\$
\refitem cmdat \\\@
\refitem cmdbackslash \\\\
\refitem cmdamp \\\&
\refitem cmdtilde \\~
\refitem cmdlt \\\<
\refitem cmdgt \\\>
\refitem cmdhash \\\#
\refitem cmdperc \\\%
\refitem cmdquot \\\"
\refitem cmdchardot \\\.
\refitem cmddcolon \::
\refitem cmdpipe \\|
\refitem cmdndash \\\--
\refitem cmdmdash \\\---
\endsecreflist

The following subsections provide a list of all commands that are recognized by
doxygen. Unrecognized commands are treated as normal text.


\htmlonly</p><center><p>\endhtmlonly
<h2>
\htmlonly --- \endhtmlonly
Structural indicators
\htmlonly --- \endhtmlonly
</h2>
\htmlonly</p></center><p>\endhtmlonly

\section cmdaddtogroup \\addtogroup <name> [(title)]
  \addindex \\addtogroup
  Defines a group just like \ref cmddefgroup "\\defgroup", but in contrast to
  that command using the same \<name\> more than once will not result in a warning,
  but rather one group with a merged documentation and the first title found in
  any of the commands.

  The title is optional, so this command can also be used to add a number of
  entities to an existing group using \c \@{ and \c \@} like this:

\verbatim
  /*! \addtogroup mygrp
   *  Additional documentation for group 'mygrp'
   *  @{
   */

  /*!
   *  A function
   */
  void func1()
  {
  }

  /*! Another function */
  void func2()
  {
  }

  /*! @} */
\endverbatim

  \sa page \ref grouping "Grouping", sections \ref cmddefgroup "\\defgroup", \ref cmdingroup "\\ingroup", and
  \ref cmdweakgroup "\\weakgroup".

<hr>
\section cmdcallgraph \\callgraph

  \addindex \\callgraph
  When this command is put in a comment block of a function or method
  and \ref cfg_have_dot "HAVE_DOT" is set to \c YES, then doxygen will
  generate a call graph for that function (provided the implementation of the
  function or method calls other documented functions). The call graph will be
  generated regardless of the value of \ref cfg_call_graph "CALL_GRAPH".
  \note The completeness (and correctness) of the call graph depends on the
  doxygen code parser which is not perfect.

  \sa section \ref cmdcallergraph "\\callergraph",
      section \ref cmdhidecallgraph "\\hidecallgraph",
      section \ref cmdhidecallergraph "\\hidecallergraph" and
      option \ref cfg_call_graph "CALL_GRAPH"

<hr>
\section cmdhidecallgraph \\hidecallgraph

  \addindex \\hidecallgraph
  When this command is put in a comment block of a function or method
  and then doxygen will not generate a call graph for that function. The
  call graph will not be generated regardless of the value of
  \ref cfg_call_graph "CALL_GRAPH".
  \note The completeness (and correctness) of the call graph depends on the
  doxygen code parser which is not perfect.

  \sa section \ref cmdcallergraph "\\callergraph",
      section \ref cmdcallgraph "\\callgraph",
      section \ref cmdhidecallergraph "\\hidecallergraph" and
      option \ref cfg_call_graph "CALL_GRAPH"

<hr>
\section cmdcallergraph \\callergraph

  \addindex \\callergraph
  When this command is put in a comment block of a function or method
  and \ref cfg_have_dot "HAVE_DOT" is set to \c YES, then doxygen will
  generate a caller graph for that function (provided the implementation of the
  function or method is called by other documented functions). The caller graph will be
  generated regardless of the value of \ref cfg_caller_graph "CALLER_GRAPH".
  \note The completeness (and correctness) of the caller graph depends on the
  doxygen code parser which is not perfect.

  \sa section \ref cmdcallgraph "\\callgraph",
      section \ref cmdhidecallgraph "\\hidecallgraph",
      section \ref cmdhidecallergraph "\\hidecallergraph" and
      option \ref cfg_caller_graph "CALLER_GRAPH"

<hr>
\section cmdhidecallergraph \\hidecallergraph

  \addindex \\hidecallergraph
  When this command is put in a comment block of a function or method
  and then doxygen will not generate a caller graph for that function. The
  caller graph will not be generated regardless of the value of
  \ref cfg_caller_graph "CALLER_GRAPH".
  \note The completeness (and correctness) of the caller graph depends on the
  doxygen code parser which is not perfect.

  \sa section \ref cmdcallergraph "\\callergraph",
      section \ref cmdcallgraph "\\callgraph",
      section \ref cmdhidecallgraph "\\hidecallgraph" and
      option \ref cfg_caller_graph "CALLER_GRAPH"

<hr>
\section cmdshowrefby \\showrefby

  \addindex \\showrefby
  When this command is put in a comment block of a function, method or variable,
  then doxygen will generate an overview for that function, method, variable of
  the, documented, funcions and methods that call / use it.
  The overview will be generated regardless of the value of
  \ref cfg_referenced_by_relation "REFERENCED_BY_RELATION".
  \note The completeness (and correctness) of the overview depends on the
  doxygen code parser which is not perfect.

  \sa section \ref cmdshowrefs "\\showrefs",
      section \ref cmdhiderefby "\\hiderefby",
      section \ref cmdhiderefs "\\hiderefs" and
      option \ref cfg_referenced_by_relation "REFERENCED_BY_RELATION"

<hr>
\section cmdhiderefby \\hiderefby

  \addindex \\hiderefby
  When this command is put in a comment block of a function, method or variable
  then doxygen will not generate an overview for that function, method or
  variable of the functions and methods that call / use it.
  The overview will not be generated regardless of the value of
  \ref cfg_referenced_by_relation "REFERENCED_BY_RELATION".
  \note The completeness (and correctness) of the overview depends on the
  doxygen code parser which is not perfect.

  \sa section \ref cmdshowrefs "\\showrefs",
      section \ref cmdshowrefby "\\showrefby",
      section \ref cmdhiderefs "\\hiderefs" and
      option \ref cfg_referenced_by_relation "REFERENCED_BY_RELATION"

<hr>
\section cmdshowrefs \\showrefs

  \addindex \\showrefs
  When this command is put in a comment block of a function or method,
  then doxygen will generate an overview for that function or method of the 
  functions and methods that call it.
  The overview will be generated regardless of the value of
  \ref cfg_references_relation "REFERENCES_RELATION".
  \note The completeness (and correctness) of the overview depends on the
  doxygen code parser which is not perfect.

  \sa section \ref cmdshowrefby "\\showrefby",
      section \ref cmdhiderefby "\\hiderefby",
      section \ref cmdhiderefs "\\hiderefs" and
      option \ref cfg_references_relation "REFERENCES_RELATION"

<hr>
\section cmdhiderefs \\hiderefs

  \addindex \\hiderefs
  When this command is put in a comment block of a function or method
  and then doxygen will not generate an overview for that function or method of
  the functions and methods that call it.
  The overview will not be generated regardless of the value of
  \ref cfg_references_relation "REFERENCES_RELATION".
  \note The completeness (and correctness) of the overview depends on the
  doxygen code parser which is not perfect.

  \sa section \ref cmdshowrefs "\\showrefs",
      section \ref cmdshowrefby "\\showrefby",
      section \ref cmdhiderefby "\\hiderefby" and
      option \ref cfg_references_relation "REFERENCES_RELATION"

<hr>
\section cmdcategory \\category <name> [<header-file>] [<header-name>]

  \addindex \\category
  For Objective-C only: Indicates that a comment block contains documentation
  for a class category with name \<name\>. The arguments are
  equal to the \ref cmdclass "\\class" command.

  \sa section \ref cmdclass "\\class".

<hr>
\section cmdclass \\class <name> [<header-file>] [<header-name>]

  \addindex \\class
  Indicates that a comment block contains documentation for a
  class with name \<name\>. Optionally a header file and a header name
  can be specified. If the header-file is specified, a link to a verbatim copy
  of the header will be included in the HTML documentation.
  The \<header-name\> argument can be used to overwrite the
  name of the link that is used in the class documentation to something other
  than \<header-file\>. This can be useful if the include name is not located
  on the default include path (like \<X11/X.h\>). With the \<header-name\>
  argument you can also specify how the include statement should look like,
  by adding either quotes or sharp brackets around the name.
  Sharp brackets are used if just the name is given. Note that the
  last two arguments can also be specified using
  the \ref cmdheaderfile "\\headerfile" command.

  \par Example:
  \include class.h
  \htmlonly
  Click <a href="examples/class/html/index.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{class_example}{Class example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

</p><hr>
\section cmddef \\def <name>

  \addindex \\def
  Indicates that a comment block contains documentation for a
  \c \#define macro.

  \par Example:
  \include define.h
  \htmlonly
  Click <a href="examples/define/html/define_8h.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{define_8h}{Define example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

</p><hr>
\section cmddefgroup \\defgroup <name> (group title)

  \addindex \\defgroup
  Indicates that a comment block contains documentation for a
  \ref modules "group" of classes, files or namespaces. This can be used to
  categorize classes, files or namespaces, and document those
  categories. You can also use groups as members of other groups,
  thus building a hierarchy of groups.

  The \<name\> argument should be a single-word identifier.

  \sa page \ref grouping "Grouping", sections \ref cmdingroup "\\ingroup", \ref cmdaddtogroup "\\addtogroup", and
  \ref cmdweakgroup "\\weakgroup".

<hr>
\section cmddir \\dir [<path fragment>]

  \addindex \\dir
  Indicates that a comment block contains documentation for a directory.
  The "path fragment" argument should include the directory name and
  enough of the path to be unique with respect to the other directories
  in the project.
  The \ref cfg_strip_from_path "STRIP_FROM_PATH" option determines what is
  stripped from the full path before it appears in the output.

<hr>
\section cmdenum \\enum <name>

  \addindex \\enum
  Indicates that a comment block contains documentation for an
  enumeration, with name \<name\>. If the enum is a member of a class and
  the documentation block is located outside the class definition,
  the scope of the class should be specified as well.
  If a comment block is located directly in front of an enum declaration,
  the \c \\enum comment may be omitted.

  \par Note:
  The type of an anonymous enum cannot be documented, but the values
  of an anonymous enum can.

  \par Example:
  \include enum.h
  \htmlonly
  Click <a href="examples/enum/html/class_enum___test.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{class_enum___test}{Enum example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

</p><hr>
\section cmdexample \\example[{lineno}] <file-name>

  \addindex \\example
  Indicates that a comment block contains documentation for a source code
  example. The name of the source file is \<file-name\>.
  The contents of this file will be included in the documentation, just after the
  documentation contained in the comment block.
  You can add option `{lineno}` to enable line numbers for the example if desired.
  All examples are placed in a list. The source code is scanned for documented members and classes.
  If any are found, the names are cross-referenced with the documentation.
  Source files or directories can be specified using the
  \ref cfg_example_path "EXAMPLE_PATH"
  tag of doxygen's configuration file.

  If \<file-name\> itself is not unique for the set of example files specified
  by the
  \ref cfg_example_path "EXAMPLE_PATH" tag, you can include part of the absolute path
  to disambiguate it.

  If more than one source file is needed for the example,
  the \ref cmdinclude "\\include" command can be used.

  \par Example:
  \include example.cpp
  Where the example file \c example_test.cpp looks as follows:
  \include example_test.cpp
  \htmlonly
  Click <a href="examples/example/html/examples.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{example_test_8cpp-example}{Example example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

  \sa section \ref cmdinclude "\\include".

</p><hr>
\section cmdendinternal \\endinternal

  \addindex \\endinternal
  This command ends a documentation fragment that was started with a
  \ref cmdinternal "\\internal" command. The text between \ref cmdinternal "\\internal" and
  \c \\endinternal will only be visible
  if \ref cfg_internal_docs "INTERNAL_DOCS" is set to \c YES.

<hr>
\section cmdextends \\extends <name>

  \addindex \\extends
  This command can be used to manually indicate an inheritance relation,
  when the programming language does not support this concept natively
  (e.g. C).

  The file \c manual.c in the example directory shows how to use this command.

  \htmlonly
  Click <a href="examples/manual/html/index.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{extends_example}{Extends example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

  \sa section \ref cmdimplements "\\implements" and section
      \ref cmdmemberof "\\memberof"

<hr>
\section cmdfile \\file [<name>]

  \addindex \\file
  Indicates that a comment block contains documentation for a source or
  header file with name \<name\>. The file name may include (part of) the
  path if the file-name alone is not unique. If the file name is omitted
  (i.e. the line after \c \\file is left blank) then the documentation block that
  contains the \c \\file command will belong to the file it is located in.

  \par Important:
  The documentation of global functions, variables, typedefs, and enums will
  only be included in the output if the file they are in is documented as well.

  \par Example:
  \include file.h
  \htmlonly
  Click <a href="examples/file/html/file_8h.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{file_example}{File example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

  \note In the above example \ref cfg_javadoc_autobrief "JAVADOC_AUTOBRIEF"
  has been set to \c YES in the configuration file.

</p><hr>
\section cmdfn \\fn (function declaration)

  \addindex \\fn
  Indicates that a comment block contains documentation for a function
  (either global or as a member of a class). This command is \em only
  needed if a comment block is \e not placed in front (or behind)
  the function declaration or definition.

  If your comment block \e is in front of the function
  declaration or definition this command can (and to avoid redundancy
  should) be omitted.

  A full function declaration including arguments should be specified after the
  \c \\fn command on a \e single line, since the argument ends at the end
  of the line!

  This command is equivalent to \ref cmdvar "\\var", \ref cmdtypedef "\\typedef",
  and \ref cmdproperty "\\property".

  \warning Do not use this command
  if it is not absolutely needed, since it will lead to duplication of
  information and thus to errors.

  \par Example:
  \include func.h
  \htmlonly
  Click <a href="examples/func/html/class_fn___test.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{class_fn___test}{Fn example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

  \sa sections \ref cmdvar "\\var", \ref cmdproperty "\\property", and
               \ref cmdtypedef "\\typedef".

</p><hr>
\section cmdheaderfile \\headerfile <header-file> [<header-name>]

  \addindex \\headerfile
  Intended to be used for class, struct, or union documentation, where
  the documentation is in front of the definition. The arguments of
  this command are the same as the second and third argument of
  \ref cmdclass "\\class".
  The \<header-file\> name refers to the file that should be included by the
  application to obtain the definition of the class, struct, or union.
  The \<header-name\> argument can be used to overwrite the
  name of the link that is used in the class documentation to something other
  than \<header-file\>. This can be useful if the include name is not located
  on the default include path (like \<X11/X.h\>).

  With the \<header-name\>
  argument you can also specify how the include statement should look like,
  by adding either double quotes or sharp brackets around the name.
  By default sharp brackets are used if just the name is given.

  If a pair of double quotes is given for either the \<header-file\> or
  \<header-name\> argument, the current file (in which the command was found)
  will be used but with quotes. So for a comment block with a \c \\headerfile
  command inside a file <code>test.h</code>, the following three commands are equivalent:
  \verbatim
  \headerfile test.h "test.h"
  \headerfile test.h ""
  \headerfile "" \endverbatim
  To get sharp brackets you do not need to specify anything,
  but if you want to be explicit you could use any of the following:
  \verbatim
  \headerfile test.h <test.h>
  \headerfile test.h <>
  \headerfile <> \endverbatim

  To globally reverse the default include representation to
  local includes you can set
  \ref cfg_force_local_includes "FORCE_LOCAL_INCLUDES" to \c YES.

  To disable the include information altogether set
  \ref cfg_show_include_files "SHOW_INCLUDE_FILES" to \c NO.

<hr>
\section cmdhideinitializer \\hideinitializer

  \addindex \\hideinitializer
  By default the value of a define and the initializer of a variable
  are displayed unless they are longer than 30 lines. By putting
  this command in a comment block of a define or variable, the
  initializer is always hidden. The maximum number of initialization lines
  can be changed by means of the configuration parameter
  \ref cfg_max_initializer_lines "MAX_INITIALIZER_LINES", the default 
  value is 30.

  \sa section \ref cmdshowinitializer "\\showinitializer".

<hr>
\section cmdidlexcept \\idlexcept <name> 
  \addindex \\idlexcept

  Indicates that a comment block contains documentation for a
  IDL exception with name \<name\>.

<hr>
\section cmdimplements \\implements <name>

  \addindex \\implements
  This command can be used to manually indicate an inheritance relation,
  when the programming language does not support this concept natively
  (e.g. C).

  The file \c manual.c in the example directory shows how to use this command.

  \htmlonly
  Click <a href="examples/manual/html/index.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{extends_example}{Implements example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

  \sa section \ref cmdextends "\\extends" and section
      \ref cmdmemberof "\\memberof"

<hr>
\section cmdingroup \\ingroup (<groupname> [<groupname> <groupname>])

  \addindex \\ingroup
  If the \c \\ingroup command is placed in a comment block of a
  class, file or namespace, then it will be added to the group or
  groups identified by \<groupname\>.

  \sa page \ref grouping "Grouping", sections \ref cmddefgroup "\\defgroup",
  \ref cmdaddtogroup "\\addtogroup", and \ref cmdweakgroup "\\weakgroup"

<hr>
\section cmdinterface \\interface <name> [<header-file>] [<header-name>]

  \addindex \\interface
  Indicates that a comment block contains documentation for an
  interface with name \<name\>. The arguments are equal to the arguments of the 
  \ref cmdclass "\\class" command.

  \sa section \ref cmdclass "\\class".

<hr>
\section cmdinternal \\internal

  \addindex \\internal
  This command starts a documentation fragment that is meant for internal
  use only. The fragment naturally ends at the end of the comment block.
  You can also force the internal section to end earlier by using the
  \ref cmdendinternal "\\endinternal" command.

  If the \c \\internal command is put inside a section
  (see for example \ref cmdsection "\\section") all subsections after the
  command are considered to be internal as well. Only a new section at the
  same level will end the fragment that is considered internal.

  You can use \ref cfg_internal_docs "INTERNAL_DOCS" in the configuration file
  to show (\c YES) or hide (\c NO) the internal documentation.

  \sa section \ref cmdendinternal "\\endinternal".


<hr>
\section cmdmainpage \\mainpage [(title)]

  \addindex \\mainpage

  If the \c \\mainpage command is placed in a comment block the
  block is used to customize the index page (in HTML) or
  the first chapter (in \LaTeX).

  The title argument is optional and replaces the default title that
  doxygen normally generates. If you do not want any title you can
  specify \c notitle as the argument of \c \\mainpage.

  Here is an example:
\verbatim
/*! \mainpage My Personal Index Page
 *
 * \section intro_sec Introduction
 *
 * This is the introduction.
 *
 * \section install_sec Installation
 *
 * \subsection step1 Step 1: Opening the box
 *
 * etc...
 */
\endverbatim

 You can refer to the main page using: <code>\ref cmdref "\\ref" index</code>.

 \sa section \ref cmdsection "\\section",
     section \ref cmdsubsection "\\subsection", and
     section \ref cmdpage "\\page".

<hr>
\section cmdmemberof \\memberof <name>

  \addindex \\memberof
  This command makes a function a member of a class in a similar way
  as \ref cmdrelates "\\relates" does, only with this command the function
  is represented as a real member of the class.
  This can be useful when the programming language does not support
  the concept of member functions natively (e.g. C).

  It is also possible to use this command together with
  \ref cmdpublic "\\public", \ref cmdprotected "\\protected" or
  \ref cmdprivate "\\private".

  The file \c manual.c in the example directory shows how to use this command.

  \htmlonly
  Click <a href="examples/manual/html/index.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly

  \sa sections \ref cmdextends "\\extends", \ref cmdimplements "\\implements",
      \ref cmdpublic "\\public", \ref cmdprotected "\\protected" and
      \ref cmdprivate "\\private".

</p><hr>
\section cmdname \\name [(header)]

  \addindex \\name

  This command turns a comment block into a header
  definition of a member group. The
  comment block should be followed by a
  <code>//\@{ ... //\@}</code> block containing the
  members of the group.

  See section \ref memgroup for an example.

<hr>
\section cmdnamespace \\namespace <name>

  \addindex \\namespace
  Indicates that a comment block contains documentation for a
  namespace with name \<name\>.

<hr>
\section cmdnosubgrouping \\nosubgrouping

  \addindex \\nosubgrouping
  This command can be put in the documentation
  of a class. It can be used in combination with member grouping
  to avoid that doxygen puts a member group as a subgroup of a
  Public/Protected/Private/... section.

  \sa sections \ref cmdpublicsection "\\publicsection",
      \ref cmdprotectedsection "\\protectedsection" and
      \ref cmdprivatesection "\\privatesection".

<hr>
\section cmdoverload \\overload [(function declaration)]

  \addindex \\overload
  This command can be used to generate the following
  standard text for an overloaded member function:

  > This is an overloaded member function, provided for convenience.
  > It differs from the above function only in what argument(s) it accepts.

  If the documentation for the overloaded member function is not located
  in front of the function declaration or definition, the optional
  argument should be used to specify the correct function.

  Any other documentation that is inside the documentation block will
  by appended after the generated message.

  \par Note 1:
    You are responsible that there is indeed an
    earlier documented member that is overloaded by this one.
    To prevent that document reorders the documentation you should set
    \ref cfg_sort_member_docs "SORT_MEMBER_DOCS" to \c NO in this case.
  \par Note 2:
    The \c \\overload command does not work inside a one-line comment.
  \par Example:
  \include overload.cpp
  \htmlonly
  Click <a href="examples/overload/html/class_overload___test.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{class_overload___test}{Overload example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

</p><hr>
\section cmdpackage \\package <name>

  \addindex \\package
  Indicates that a comment block contains documentation for a
  Java package with name \<name\>.

<hr>
\section cmdpage \\page <name> (title)

  \addindex \\page
  Indicates that a comment block contains a piece of documentation that is
  not directly related to one specific class, file or member.
  The HTML generator creates a page containing the documentation. The
  \LaTeX generator
  starts a new section in the chapter 'Page documentation'.

  \par Example:
  \include page.doc
  \htmlonly
  Click <a href="examples/page/html/pages.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{page_example}{Page example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

  \par Note:
     The \<name\> argument consists of a combination of letters and number
     digits. If you wish to use upper case letters (e.g. \c MYPAGE1), or
     mixed case letters (e.g. \c MyPage1) in the \<name\> argument, you
     should set \ref cfg_case_sense_names "CASE_SENSE_NAMES" to \c YES. However, this is advisable
     only if your file system is case sensitive. Otherwise (and for better
     portability) you should use all lower case letters (e.g. \c mypage1)
     for \<name\> in all references to the page.

  \sa section \ref cmdsection "\\section", section
              \ref cmdsubsection "\\subsection", and section
              \ref cmdref "\\ref".

</p><hr>
\section cmdprivate \\private

  \addindex \\private
  Indicates that the member documented by the comment block is private,
  i.e., should only be accessed by other members in the same class.

  Note that doxygen automatically detects the protection level of members
  in object-oriented languages. This command is intended for use only when
  the language does not support the concept of protection level natively
  (e.g. C, PHP 4).

  For starting a section of private members, in a way similar to the
  "private:" class marker in C++, use \ref cmdprivatesection "\\privatesection".

  \sa sections \ref cmdmemberof "\\memberof", \ref cmdpublic "\\public",
      \ref cmdprotected "\\protected" and \ref cmdprivatesection "\\privatesection".

<hr>
\section cmdprivatesection \\privatesection

  \addindex \\privatesection
  Starting a section of private members, in a way similar to the
  "private:" class marker in C++.
  Indicates that the member documented by the comment block is private,
  i.e., should only be accessed by other members in the same class.

  \sa sections \ref cmdmemberof "\\memberof", \ref cmdpublic "\\public",
      \ref cmdprotected "\\protected" and \ref cmdprivate "\\private".

<hr>
\section cmdproperty \\property (qualified property name)

  \addindex \\property
  Indicates that a comment block contains documentation for a
  property (either global or as a member of a class).
  This command is equivalent to \ref cmdfn "\\fn",
  \ref cmdtypedef "\\typedef", and \ref cmdvar "\\var".

  \sa sections \ref cmdfn "\\fn", \ref cmdtypedef "\\typedef", and
               \ref cmdvar "\\var".

<hr>
\section cmdprotected \\protected

  \addindex \\protected
  Indicates that the member documented by the comment block is protected,
  i.e., should only be accessed by other members in the same or derived
  classes.

  Note that doxygen automatically detects the protection level of members
  in object-oriented languages. This command is intended for use only when
  the language does not support the concept of protection level natively
  (e.g. C, PHP 4).

  For starting a section of protected members, in a way similar to the
  "protected:" class marker in C++, use \ref cmdprotectedsection "\\protectedsection".

  \sa sections \ref cmdmemberof "\\memberof", \ref cmdpublic "\\public",
      \ref cmdprivate "\\private" and \ref cmdprotectedsection "\\protectedsection".

<hr>
\section cmdprotectedsection \\protectedsection

  \addindex \\protectedsection
  Starting a section of protected members, in a way similar to the
  "protected:" class marker in C++.
  Indicates that the member documented by the comment block is protected,
  i.e., should only be accessed by other members in the same or derived
  classes.

  \sa sections \ref cmdmemberof "\\memberof", \ref cmdpublic "\\public",
      \ref cmdprivate "\\private" and \ref cmdprotected "\\protected".

<hr>
\section cmdprotocol \\protocol <name> [<header-file>] [<header-name>]

  \addindex \\protocol
  Indicates that a comment block contains documentation for a
  protocol in Objective-C with name \<name\>. The arguments are equal
  to the \ref cmdclass "\\class" command.

  \sa section \ref cmdclass "\\class".

<hr>
\section cmdpublic \\public

  \addindex \\public
  Indicates that the member documented by the comment block is public,
  i.e., can be accessed by any other class or function.

  Note that doxygen automatically detects the protection level of members
  in object-oriented languages. This command is intended for use only when
  the language does not support the concept of protection level natively
  (e.g. C, PHP 4).

  For starting a section of public members, in a way similar to the
  "public:" class marker in C++, use \ref cmdpublicsection "\\publicsection".

  \sa sections \ref cmdmemberof "\\memberof", \ref cmdprotected "\\protected",
      \ref cmdprivate "\\private" and \ref cmdpublicsection "\\publicsection".

<hr>
\section cmdpublicsection \\publicsection

  \addindex \\publicsection
  Starting a section of public members, in a way similar to the
  "public:" class marker in C++.
  Indicates that the member documented by the comment block is public,
  i.e., can be accessed by any other class or function.

  \sa sections \ref cmdmemberof "\\memberof", \ref cmdprotected "\\protected",
      \ref cmdprivate "\\private" and \ref cmdpublic "\\public".

<hr>
\section cmdpure \\pure

  \addindex \\pure
  Indicates that the member documented by the comment block is pure virtual,
  i.e., it is abstract and has no implementation associated with it.

  This command is intended for use only when
  the language does not support the concept of pure virtual methods natively
  (e.g. C, PHP 4).

<hr>
\section cmdrelates \\relates <name>

  \addindex \\relates
  This command can be used in the documentation of a non-member function
  \<name\>. It puts the function inside the 'related function' section
  of the class documentation. This command is useful for documenting
  non-friend functions that are nevertheless strongly coupled to a certain
  class. It prevents the need of having to document a file, but
  only works for functions.

  \par Example:
  \include relates.cpp
  \htmlonly
  Click <a href="examples/relates/html/class_string.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{class_string}{Relates example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

</p><hr>
\section cmdrelated \\related <name>

  \addindex \\related
  Equivalent to \ref cmdrelates "\\relates"

<hr>
\section cmdrelatesalso \\relatesalso <name>

  \addindex \\relatesalso
  This command can be used in the documentation of a non-member function
  \<name\>. It puts the function both inside the 'related function' section
  of the class documentation as well as leaving it at its normal file documentation
  location. This command is useful for documenting
  non-friend functions that are nevertheless strongly coupled to a certain
  class. It only works for functions.

<hr>
\section cmdrelatedalso \\relatedalso <name>

  \addindex \\relatedalso
  Equivalent to \ref cmdrelatesalso "\\relatesalso"

<hr>
\section cmdshowinitializer \\showinitializer

  \addindex \\showinitializer
  By default the value of a define and the initializer of a variable
  are only displayed if they are less than 30 lines long. By putting
  this command in a comment block of a define or variable, the
  initializer is shown unconditionally.
  The maximum number of initialization lines
  can be changed by means of the configuration parameter
  \ref cfg_max_initializer_lines "MAX_INITIALIZER_LINES", the default value is
  30.

  \sa section \ref cmdhideinitializer "\\hideinitializer".

<hr>
\section cmdstatic \\static

  \addindex \\static
  Indicates that the member documented by the comment block is static,
  i.e., it works on a class, instead of on an instance of the class.

  This command is intended for use only when
  the language does not support the concept of static methods natively (e.g. C).

<hr>
\section cmdstruct \\struct <name> [<header-file>] [<header-name>]

  \addindex \\struct
  Indicates that a comment block contains documentation for a
  struct with name \<name\>. The arguments are equal to the arguments of the 
  \ref cmdclass "\\class" command.

  \sa section \ref cmdclass "\\class".

<hr>
\section cmdtypedef \\typedef (typedef declaration)

  \addindex \\typedef
  Indicates that a comment block contains documentation for a
  typedef (either global or as a member of a class).
  This command is equivalent to \ref cmdfn "\\fn",
  \ref cmdproperty "\\property", and \ref cmdvar "\\var".

  \sa section \ref cmdfn "\\fn", \ref cmdproperty "\\property", and
              \ref cmdvar "\\var".

<hr>
\section cmdunion \\union <name> [<header-file>] [<header-name>]

  \addindex \\union
  Indicates that a comment block contains documentation for a
  union with name \<name\>. The arguments are equal to the arguments of the 
  \ref cmdclass "\\class" command.

  \sa section \ref cmdclass "\\class".

<hr>
\section cmdvar \\var (variable declaration)

  \addindex \\var
  Indicates that a comment block contains documentation for a variable or
  enum value (either global or as a member of a class).
  This command is equivalent to \ref cmdfn "\\fn",
  \ref cmdproperty "\\property", and \ref cmdtypedef "\\typedef".

  Note that for PHP one can also specify the type of the variable.
  The syntax is similar as for the `phpDocumentor` but the description has to start
  at the next line, i.e.
\verbatim
@var  datatype $varname
Description
\endverbatim

  \sa section \ref cmdfn "\\fn", \ref cmdproperty "\\property", and \ref cmdtypedef "\\typedef".

<hr>
\section cmdvhdlflow \\vhdlflow [(title for the flow chart)]

  \addindex \\vhdlflow
  This is a VHDL specific command, which can be put in the documentation of a process to
  produce a flow chart of the logic in the process. 
  Optionally a title for the flow chart can be given.
  \note Currently the flow chart will only appear in the HTML output.

<hr>
\section cmdweakgroup \\weakgroup <name> [(title)]
  \addindex \\weakgroup
  Can be used exactly like \ref cmdaddtogroup "\\addtogroup", but has
  a lower priority when it comes to resolving conflicting grouping
  definitions.

  \sa page \ref grouping "Grouping" and section \ref cmdaddtogroup "\\addtogroup".

<hr>

\htmlonly</p><center><p>\endhtmlonly
<h2>
\htmlonly --- \endhtmlonly
Section indicators
\htmlonly --- \endhtmlonly
</h2>
\htmlonly</p></center><p>\endhtmlonly

<hr>
\section cmdattention \\attention { attention text }

  \addindex \\attention
  Starts a paragraph where a message that needs attention may be entered.
  The paragraph will be indented.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\attention commands will be joined into a single paragraph.
  The \c \\attention command ends when a blank line or some other
  sectioning command is encountered.

<hr>
\section cmdauthor \\author { list of authors }

  \addindex \\author
  Starts a paragraph where one or more author names may be entered.
  The paragraph will be indented.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\author commands will be joined into a single paragraph.
  Each author description will start a new line. Alternatively, one \c \\author command
  may mention several authors. The \c \\author command ends when a blank line or some other
  sectioning command is encountered.

  \par Example:
  \include author.cpp
  \htmlonly
  Click <a href="examples/author/html/class_some_nice_class.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{class_some_nice_class}{Author example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

</p><hr>
\section cmdauthors \\authors { list of authors }

  \addindex \\authors
  Equivalent to \ref cmdauthor "\\author".

<hr>
\section cmdbrief \\brief { brief description }

  \addindex \\brief
  Starts a paragraph that serves as a brief description. For classes and files
  the brief description will be used in lists and at the start of the
  documentation page. For class and file members, the brief description
  will be placed at the declaration of the member and prepended to the
  detailed description. A brief description may span several lines (although
  it is advised to keep it brief!). A brief description ends when a
  blank line or another sectioning command is encountered. If multiple
  \c \\brief commands are present they will be joined. See section
  \ref cmdauthor "\\author" for an example.

  Synonymous to \ref cmdshort "\\short".

<hr>
\section cmdbug \\bug { bug description }

  \addindex \\bug
  Starts a paragraph where one or more bugs may be reported.
  The paragraph will be indented.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\bug commands will be joined into a single paragraph.
  Each bug description will start on a new line.
  Alternatively, one \c \\bug command may mention
  several bugs. The \c \\bug command ends when a blank line or some other
  sectioning command is encountered. See section \ref cmdauthor "\\author"
  for an example.

<hr>
\section cmdcond \\cond [(section-label)]

  \addindex \\cond
  Starts a conditional section that ends with a corresponding
  \ref cmdendcond "\\endcond" command, which is typically found in
  another comment block. The main purpose of this pair of
  commands is to (conditionally) exclude part of a file from processing
  (in older version of doxygen this could only be achieved using C preprocessor commands).

  The section between \c \\cond and \ref cmdendcond "\\endcond" can be included by
  adding its section label to the \ref cfg_enabled_sections "ENABLED_SECTIONS"
  configuration option. If the section label is omitted, the section will
  be excluded from processing unconditionally. The section label can be a 
  logical expression build of section labels, round brackets, && (AND), || (OR) and ! (NOT).
  If you use an expression you need to wrap it in round brackets, i.e 
  <tt>\\cond (!LABEL1 && LABEL2)</tt>.

  For conditional sections within a comment block one should
  use a \ref cmdif "\\if" ... \ref cmdendif "\\endif" block.

  Conditional sections can be nested. In this case a nested section will only
  be shown if it and its containing section are included.

  Here is an example showing the commands in action:

\verbatim
/** An interface */
class Intf
{
  public:
    /** A method */
    virtual void func() = 0;

    /// @cond TEST

    /** A method used for testing */
    virtual void test() = 0;

    /// @endcond
};

/// @cond DEV
/*
 *  The implementation of the interface
 */
class Implementation : public Intf
{
  public:
    void func();

    /// @cond TEST
    void test();
    /// @endcond

    /// @cond
    /** This method is obsolete and does
     *  not show up in the documentation.
     */
    void obsolete();
    /// @endcond
};

/// @endcond
\endverbatim

The output will be different depending on whether or not \ref cfg_enabled_sections "ENABLED_SECTIONS"
contains \c TEST, or \c DEV

  \sa sections \ref cmdendcond "\\endcond" and  \ref cfg_enabled_sections "ENABLED_SECTIONS".
  \note Due to the moment of parsing the \c \\cond and \ref cmdendcond "\\endcond" commands cannot
  be used in \ref cfg_aliases "ALIASES".

<hr>
\section cmdcopyright \\copyright { copyright description }

  \addindex \\copyright
  Starts a paragraph where the copyright of an entity can be described.
  This paragraph will be indented.
  The text of the paragraph has no special internal structure.
  See section \ref cmdauthor "\\author" for an example.

<hr>
\section cmddate \\date { date description }

  \addindex \\date
  Starts a paragraph where one or more dates may be entered.
  The paragraph will be indented.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\date commands will be joined into a single paragraph.
  Each date description will start on a new line.
  Alternatively, one \c \\date command may mention
  several dates. The \c \\date command ends when a blank line or some other
  sectioning command is encountered. See section \ref cmdauthor "\\author"
  for an example.

<hr>
\section cmddeprecated \\deprecated { description }

  \addindex \\deprecated
  Starts a paragraph indicating that this documentation block belongs to
  a deprecated entity. Can be used to describe alternatives,
  expected life span, etc.

<hr>
\section cmddetails \\details { detailed description }

  \addindex \\details
  Just like \ref cmdbrief "\\brief" starts a brief description, \c \\details
  starts the detailed description. You can also start a new paragraph (blank line)
  then the \c \\details command is not needed.

<hr>
\section cmdelse \\else

  \addindex \\else
  Starts a conditional section if the previous conditional section
  was not enabled. The previous section should have been started with
  a \ref cmdif "\\if", \ref cmdifnot "\\ifnot", or \ref cmdelseif "\\elseif"
  command.

  \sa \ref cmdif "\\if", \ref cmdifnot "\\ifnot", \ref cmdelseif "\\elseif",
      \ref cmdendif "\\endif."

<hr>
\section cmdelseif \\elseif (section-label)

  \addindex \\elseif
  Starts a conditional documentation section if the previous section
  was not enabled. A conditional section is
  disabled by default. To enable it you must put the
  section-label after the \ref cfg_enabled_sections "ENABLED_SECTIONS"
  tag in the configuration file.  The section label can be a logical expression
  build of section names, round brackets, && (AND), || (OR) and ! (NOT).
  Conditional blocks can be nested. A nested section is
  only enabled if all enclosing sections are enabled as well.

  \sa sections \ref cmdendif "\\endif", \ref cmdifnot "\\ifnot",
              \ref cmdelse "\\else", and \ref cmdelseif "\\elseif".

<hr>
\section cmdendcond \\endcond

  \addindex \\endcond
  Ends a conditional section that was started by \ref cmdcond "\\cond".

  \sa section \ref cmdcond "\\cond".
  \note Due to the moment of parsing the \c \\endcond and \ref cmdcond "\\cond" commands cannot
  be used in \ref cfg_aliases "ALIASES".

<hr>
\section cmdendif \\endif

  \addindex \\endif
  Ends a conditional section that was started by \ref cmdif "\\if" or \ref cmdifnot "\\ifnot"
  For each \ref cmdif "\\if" or \ref cmdifnot "\\ifnot" one and only one matching 
  \ref cmdendif "\\endif" must follow.

  \sa sections \ref cmdif "\\if" and \ref cmdifnot "\\ifnot".

<hr>
\section cmdexception \\exception <exception-object> { exception description }

  \addindex \\exception
  Starts an exception description for an exception object with name
  \<exception-object\>. Followed by a description of the exception.
  The existence of the exception object is not checked.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\exception commands will be joined into a single paragraph.
  Each exception description will start on a new line.
  The \c \\exception description ends when a blank line or some other
  sectioning command is encountered. See section \ref cmdfn "\\fn" for an
  example.

<hr>
\section cmdif \\if (section-label)

  \addindex \\if
  Starts a conditional documentation section. The section ends
  with a matching \ref cmdendif "\\endif" command. A conditional section is
  disabled by default. To enable it you must put the
  section-label after the \ref cfg_enabled_sections "ENABLED_SECTIONS"
  tag in the configuration file.  

  The section label can be a logical expression
  build of section names, round brackets, && (AND), || (OR) and ! (NOT).
  If you use an expression you need to wrap it in round brackets, i.e 
  <tt>\\cond (!LABEL1 && LABEL2)</tt>.

  Conditional blocks can be nested. A nested section is
  only enabled if all enclosing sections are enabled as well.

  \par Example:
\verbatim
  /*! Unconditionally shown documentation.
   *  \if Cond1
   *    Only included if Cond1 is set.
   *  \endif
   *  \if Cond2
   *    Only included if Cond2 is set.
   *    \if Cond3
   *      Only included if Cond2 and Cond3 are set.
   *    \endif
   *    More text.
   *  \endif
   *  Unconditional text.
   */
\endverbatim

  You can also use conditional commands inside aliases. To
  document a class in two languages you could for instance use:

\par Example 2:
\verbatim
/*! \english
 *  This is English.
 *  \endenglish
 *  \dutch
 *  Dit is Nederlands.
 *  \enddutch
 */
class Example
{
};
\endverbatim

  Where the following aliases are defined in the configuration file:

\verbatim
ALIASES  = "english=\if english" \
           "endenglish=\endif" \
           "dutch=\if dutch" \
           "enddutch=\endif"
\endverbatim

  and \ref cfg_enabled_sections "ENABLED_SECTIONS" can be used to enable either \c english or \c dutch.

  \sa sections \ref cmdendif "\\endif", \ref cmdifnot "\\ifnot",
               \ref cmdelse "\\else", \ref cmdelseif "\\elseif", and
               \ref cfg_enabled_sections "ENABLED_SECTIONS".

<hr>
\section cmdifnot \\ifnot (section-label)

  \addindex \\ifnot
  Starts a conditional documentation section. The section ends
  with a matching \ref cmdendif "\\endif" command. This conditional section is
  enabled by default. To disable it you must put the
  section-label after the \ref cfg_enabled_sections "ENABLED_SECTIONS"
  tag in the configuration file.  The section label can be a logical expression
  build of section names, round brackets, && (AND), || (OR) and ! (NOT).

  \sa sections \ref cmdendif "\\endif", \ref cmdif "\\if",
               \ref cmdelse "\\else", and \ref cmdelseif "\\elseif", and
               \ref cfg_enabled_sections "ENABLED_SECTIONS".

<hr>
\section cmdinvariant \\invariant { description of invariant }

  \addindex \\invariant
  Starts a paragraph where the invariant of an entity can be described.
  The paragraph will be indented.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\invariant commands will be joined into a single paragraph.
  Each invariant description will start on a new line.
  Alternatively, one \c \\invariant command may mention
  several invariants. The \c \\invariant command ends when a blank line or some other
  sectioning command is encountered.

<hr>
\section cmdnote \\note { text }

  \addindex \\note
  Starts a paragraph where a note can be entered. The paragraph will be
  indented. The text of the paragraph has no special internal structure.
  All visual enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\note commands will be joined into a single paragraph.
  Each note description will start on a new line.
  Alternatively, one \c \\note command may mention
  several notes. The \c \\note command ends when a blank line or some other
  sectioning command is encountered. See section \ref cmdpar "\\par"
  for an example.

<hr>
\section cmdpar \\par [(paragraph title)] { paragraph }

  \addindex \\par
  If a paragraph title is given this command starts a paragraph with a
  user defined heading. The heading extends until the end of the
  line. The paragraph following the command will be indented.

  If no paragraph title is given this command will start a new paragraph.
  This will also work inside other paragraph commands
  (like \ref cmdparam "\\param" or \ref cmdwarning "\\warning") without ending that command.

  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  The \c \\par command ends when a blank line or some other
  sectioning command is encountered.

  \par Example:
  \include par.cpp
  \htmlonly
  Click <a href="examples/par/html/class_par___test.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{class_par___test}{Par example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

</p><hr>
\section cmdparam \\param [(dir)] <parameter-name> { parameter description }

  \addindex \\param
  Starts a parameter description for a function parameter with name
  \<parameter-name\>, followed by a description of the parameter.
  The existence of the parameter is checked and a warning is given if
  the documentation of this (or any other) parameter is missing or not
  present in the function declaration or definition.

  The \c \\param command has an optional attribute, (dir), specifying the direction
  of the parameter. Possible values are "[in]", "[in,out]", and "[out]",
  note the [square] brackets in this description.
  When a parameter is both input and output, [in,out] is used as attribute.
  Here is an example for the function \c memcpy:
  \code
/*!
 * Copies bytes from a source memory area to a destination memory area,
 * where both areas may not overlap.
 * @param[out] dest The memory area to copy to.
 * @param[in]  src  The memory area to copy from.
 * @param[in]  n    The number of bytes to copy
 */
void memcpy(void *dest, const void *src, size_t n);
  \endcode

  The parameter description is a paragraph with no special internal structure.
  All visual enhancement commands may be used inside the paragraph.

  Multiple adjacent \c \\param commands will be joined into a single paragraph.
  Each parameter description will start on a new line.
  The \c \\param description ends when a blank line or some other
  sectioning command is encountered. See section \ref cmdfn "\\fn" for an
  example.

  Note that you can also document multiple parameters with a single
  \c \\param command using a comma separated list. Here is an example:

\code
/** Sets the position.
 *  @param x,y,z Coordinates of the position in 3D space.
 */
void setPosition(double x,double y,double z,double t)
{
}
\endcode

  Note that for PHP one can also specify the type (or types if you
  separate them with a pipe symbol) which are allowed for a parameter
  (as this is not part of the definition).
  The syntax is the same as for the `phpDocumentor`, i.e.
\verbatim
@param  datatype1|datatype2 $paramname description
\endverbatim

<hr>
\section cmdparblock \\parblock
  \addindex \\parblock
  For commands that expect a single paragraph as argument
  (such as \ref cmdpar "\\par", \ref cmdparam "\\param" and \ref cmdwarning "\\warning"),
  the \ref cmdparblock "\\parblock" command allows to start a
  description that covers multiple paragraphs, which then ends with
  \ref cmdendparblock "\\endparblock".

  Example:
\verbatim
/** Example of a param command with a description consisting of two paragraphs
 *  \param p 
 *  \parblock
 *  First paragraph of the param description.
 *
 *  Second paragraph of the param description.
 *  \endparblock
 *  Rest of the comment block continues.
 */
\endverbatim
  Note that the \c \\parblock command may also appear directly after
  \ref cmdparam "\\param"'s first argument.

<hr>
\section cmdendparblock \\endparblock
  \addindex \\endparblock
  This ends a block of paragraphs started with \ref cmdparblock "\\parblock".

<hr>
\section cmdtparam \\tparam <template-parameter-name> { description }

  \addindex \\tparam
  Starts a template parameter for a class or function template parameter
  with name \<template-parameter-name\>, followed by a description of the
  template parameter.

  Otherwise similar to \ref cmdparam "\\param".

<hr>
\section cmdpost \\post { description of the postcondition }

  \addindex \\post
  Starts a paragraph where the postcondition of an entity can be described.
  The paragraph will be indented.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\post commands will be joined into a single paragraph.
  Each postcondition will start on a new line.
  Alternatively, one \c \\post command may mention
  several postconditions. The \c \\post command ends when a blank line or some other
  sectioning command is encountered.

<hr>
\section cmdpre \\pre { description of the precondition }

  \addindex \\pre
  Starts a paragraph where the precondition of an entity can be described.
  The paragraph will be indented.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\pre commands will be joined into a single paragraph.
  Each precondition will start on a new line.
  Alternatively, one \c \\pre command may mention
  several preconditions. The \c \\pre command ends when a blank line or some other
  sectioning command is encountered.

<hr>
\section cmdremark \\remark { remark text }

  \addindex \\remark
  Starts a paragraph where one or more remarks may be entered.
  The paragraph will be indented.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\remark commands will be joined into a single paragraph.
  Each remark will start on a new line.
  Alternatively, one \c \\remark command may mention
  several remarks. The \c \\remark command ends when a blank line or some other
  sectioning command is encountered.

<hr>
\section cmdremarks \\remarks { remark text }

  \addindex \\remarks
  Equivalent to \ref cmdremark "\\remark".

<hr>
\section cmdresult \\result { description of the result value }

  \addindex \\result
  Equivalent to \ref cmdreturn "\\return".

<hr>
\section cmdreturn \\return { description of the return value }

  \addindex \\return
  Starts a return value description for a function.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\return commands will be joined into a single paragraph.
  The \c \\return description ends when a blank line or some other
  sectioning command is encountered. See section \ref cmdfn "\\fn" for an
  example.

<hr>
\section cmdreturns \\returns { description of the return value }

  \addindex \\returns
  Equivalent to \ref cmdreturn "\\return".

<hr>
\section cmdretval \\retval <return value> { description }

  \addindex \\retval
  Starts a description for a function's return value with name
  \<return value\>, followed by a description of the return value.
  The text of the paragraph that forms the description has no special
  internal structure. All visual enhancement commands may be used inside the
  paragraph.
  Multiple adjacent \c \\retval commands will be joined into a single paragraph.
  Each return value description will start on a new line.
  The \c \\retval description ends when a blank line or some other
  sectioning command is encountered.

<hr>
\section cmdsa \\sa { references }

  \addindex \\sa
  Starts a paragraph where one or more cross-references to classes,
  functions, methods, variables, files or URL may be specified.
  Two names joined by either <code>::</code> or <code>\#</code>
  are understood as referring to a class and one of its members.
  One of several overloaded methods or constructors
  may be selected by including a parenthesized list of argument types after
  the method name.

  Synonymous to \ref cmdsee "\\see".

  \sa section \ref autolink "autolink" for information on how to create links
      to objects.

<hr>
\section cmdsee \\see { references }

  \addindex \\see
  Equivalent to \ref cmdsa "\\sa". Introduced for compatibility with Javadoc.

<hr>
\section cmdshort \\short { short description }

  \addindex \\short
  Equivalent to \ref cmdbrief "\\brief".

<hr>
\section cmdsince \\since { text }

  \addindex \\since
  This command can be used to specify since when (version or time) an
  entity is available. The paragraph that follows \c \\since does not have any
  special internal structure. All visual enhancement commands may be
  used inside the paragraph. The \c \\since description ends when a blank
  line or some other sectioning command is encountered.

<hr>
\section cmdtest \\test { paragraph describing a test case }

  \addindex \\test
  Starts a paragraph where a test case can be described.
  The description will also add the test case to a separate test list.
  The two instances of the description will be cross-referenced.
  Each test case in the test list will be preceded by a header that
  indicates the origin of the test case.

<hr>
\section cmdthrow \\throw <exception-object> { exception description }

  \addindex \\throw
  Synonymous \ref cmdexception "\\exception".

  \par Note:
  the command \ref cmdthrows "\\throws" is a synonym for this command.

  \sa section \ref cmdexception "\\exception"

<hr>
\section cmdthrows \\throws <exception-object> { exception description }

  \addindex \\throws
  Equivalent to \ref cmdthrow "\\throw".

<hr>
\section cmdtodo \\todo { paragraph describing what is to be done }

  \addindex \\todo
  Starts a paragraph where a TODO item is described.
  The description will also add an item to a separate TODO list.
  The two instances of the description will be cross-referenced.
  Each item in the TODO list will be preceded by a header that
  indicates the origin of the item.

<hr>
\section cmdversion \\version { version number }

  \addindex \\version
  Starts a paragraph where one or more version strings may be entered.
  The paragraph will be indented.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\version commands will be joined into a single paragraph.
  Each version description will start on a new line.
  Alternatively, one \c \\version command may mention
  several version strings.
  The \\version command ends when a blank line or some other
  sectioning command is encountered. 
  See section \ref cmdauthor "\\author" for an example.

<hr>
\section cmdwarning \\warning { warning message }

  \addindex \\warning
  Starts a paragraph where one or more warning messages may be entered.
  The paragraph will be indented.
  The text of the paragraph has no special internal structure. All visual
  enhancement commands may be used inside the paragraph.
  Multiple adjacent \c \\warning commands will be joined into a single paragraph.
  Each warning description will start on a new line.
  Alternatively, one \c \\warning command may mention
  several warnings. The \c \\warning command ends when a blank line or some other
  sectioning command is encountered. See section \ref cmdauthor "\\author"
  for an example.

<hr>
\section cmdxrefitem \\xrefitem <key> "(heading)" "(list title)" { text }

 \addindex \\xrefitem
 This command is a generalization of commands such as \ref cmdtodo "\\todo"
 and \ref cmdbug "\\bug".
 It can be used to create user-defined text sections which are automatically
 cross-referenced between the place of occurrence and a related page,
 which will be generated. On the related page all sections of
 the same type will be collected.

 The first argument \<key\> is an
 identifier uniquely representing the type of the section. The second argument
 is a quoted string representing the heading of the section under which
 text passed as the fourth argument is put. The third argument (list title)
 is used as the title for the related page containing all items with the
 same key. The keys \c "todo", \c "test", \c "bug" and \c "deprecated" are predefined.

 To get an idea on how to use the \c \\xrefitem command and what its effect
 is, consider the todo list, which (for English output) can be seen an
 alias for the command
 \verbatim \xrefitem todo "Todo" "Todo List" \endverbatim

 Since it is very tedious and error-prone to repeat the first three
 parameters of the command for each section, the command is meant to
 be used in combination with the \ref cfg_aliases "ALIASES" option in the
 configuration file.
 To define a new command \c \\reminder, for instance, one should add the following
 line to the configuration file:
 \verbatim ALIASES += "reminder=\xrefitem reminders \"Reminder\" \"Reminders\"" \endverbatim
 Note the use of escaped quotes for the second and third argument of the
 \c \\xrefitem command.

 In case parameter "(heading)" is the empty string no heading is generated. This can be useful
 when used in combination with the \ref cmdpage "\\page" command e.g.
\verbatim
/** @page my_errors My Errors
 *  @brief Errors page
 *
 *  Errors page contents.
 */

/** \error ERROR 101: in case a file can not be opened.
    Check about file system read/write access. */
#define MY_ERR_CANNOT_OPEN_FILE                   101

/** \error ERROR 102: in case a file can not be closed.
    Check about file system read/write access. */
#define MY_ERR_CANNOT_CLOSE_FILE                  102
\endverbatim
 with \c \\error defined as
 \verbatim ALIASES += "error=\xrefitem my_errors \"\" \"\"" \endverbatim

<hr>

\htmlonly</p><center><p>\endhtmlonly
<h2>
\htmlonly --- \endhtmlonly
Commands to create links
\htmlonly --- \endhtmlonly
</h2>
\htmlonly</p></center><p>\endhtmlonly

<hr>
\section cmdaddindex \\addindex (text)

  \addindex \\addindex
  This command adds (text) to the \LaTeX , DocBook and RTF index.

<hr>
\section cmdanchor \\anchor <word>

  \addindex \\anchor
  This command places an invisible, named anchor into the documentation
  to which you can refer with the \ref cmdref "\\ref" command.

  \note Anchors can currently only be put into a comment block
  that is marked as a page (using \ref cmdpage "\\page") or mainpage
  (\ref cmdmainpage "\\mainpage").

  \sa section \ref cmdref "\\ref".

<hr>
\section cmdcite \\cite <label>

  \addindex \\cite
  Adds a bibliographic reference in the text and in the list of bibliographic
  references. The \<label\> must be a valid BibTeX label that can be found 
  in one of the .bib files listed in \ref cfg_cite_bib_files "CITE_BIB_FILES".  
  For the \LaTeX output the formatting of the reference in the text can be 
  configured with \ref cfg_latex_bib_style "LATEX_BIB_STYLE". For other
  output formats a fixed representation is used. Note that using this
  command requires the \c bibtex tool to be present in the search path.

<hr>
\section cmdendlink \\endlink

  \addindex \\endlink
  This command ends a link that is started with the \ref cmdlink "\\link" command.

  \sa section \ref cmdlink "\\link".

<hr>
\section cmdlink \\link <link-object>

  \addindex \\link
  The links that are automatically generated by doxygen always have the
  name of the object they point to as link-text.

  The \c \\link command can be used to create a link to an object (a file,
  class, or member) with a user specified link-text.
  The link command should end with an \ref cmdendlink "\\endlink" command. All text between
  the \c \\link and \ref cmdendlink "\\endlink" commands serves as text for a link to
  the \<link-object\> specified as the first argument of \c \\link.

  \sa Section \ref autolink "autolink" for more information on automatically
  generated links and valid link-objects.

<hr>
\section cmdref \\ref <name> ["(text)"]

  \addindex \\ref
  Creates a reference to a named section, subsection, page or anchor.
  For HTML documentation the reference command will generate a link to
  the section. For a section or subsection the title of the section will be
  used as the text of the link. For an anchor the optional text between quotes
  will be used or \<name\> if no text is specified.
  For \LaTeX documentation the reference command will
  generate a section number for sections or the text followed by a
  page number if \<name\> refers to an anchor.

  \sa
    Section \ref cmdpage "\\page" for an example of the \c \\ref command.

<hr>
\section cmdrefitem \\refitem <name>
  \addindex \\refitem
  Just like the \ref cmdref "\\ref" command, this command creates a reference 
  to a named section, but this reference appears in a list that is started by 
  \ref cmdsecreflist "\\secreflist"
  and ends with \ref cmdendsecreflist "\\endsecreflist".
  An example of such a list can be seen 
  \ref showsecreflist "at the top of the page".

<hr>
\section cmdsecreflist \\secreflist
  \addindex \\secreflist
  Starts an index list of item, created with \ref cmdrefitem "\\refitem" 
  that each link to a named section.

<hr>
\section cmdendsecreflist \\endsecreflist
  \addindex \\endsecreflist
  End an index list started with \ref cmdsecreflist "\\secreflist".

<hr>
\section cmdsubpage \\subpage <name> ["(text)"]

  \addindex \\subpage
  This command can be used to create a hierarchy of pages. The
  same structure can be made using the \ref cmddefgroup "\\defgroup" and
  \ref cmdingroup "\\ingroup" commands, but for pages the \c \\subpage command
  is often more convenient. The main page (see \ref cmdmainpage "\\mainpage")
  is typically the root of hierarchy.

  This command behaves similar as \ref cmdref "\\ref" in the sense that
  it creates a reference to a page labeled \<name\> with the optional
  link text as specified in the second argument.

  It differs from the \ref cmdref "\\ref" command in that it only works for pages,
  and creates a parent-child relation between pages, where the
  child page (or sub page) is identified by label \<name\>.

  See the \ref cmdsection "\\section"
  and \ref cmdsubsection "\\subsection" commands if you want to add structure
  without creating multiple pages.

  \note Each page can be the sub page of only one other page and
  no cyclic relations are allowed, i.e. the page hierarchy must have a tree
  structure.

  Here is an example:
\verbatim
/*! \mainpage A simple manual

Some general info.

This manual is divided in the following sections:
- \subpage intro
- \subpage advanced "Advanced usage"
*/

//-----------------------------------------------------------

/*! \page intro Introduction
This page introduces the user to the topic.
Now you can proceed to the \ref advanced "advanced section".
*/

//-----------------------------------------------------------

/*! \page advanced Advanced Usage
This page is for advanced users.
Make sure you have first read \ref intro "the introduction".
*/
\endverbatim

<hr>
\section cmdtableofcontents \\tableofcontents['{'[option[:level]][,option[:level]]*'}']

  \addindex \\tableofcontents
  Creates a table of contents at the top of a page, listing all
  sections and subsections in the page. The `option` can be `HTML` or `LaTeX`
  or `XML` or `DocBook`. When a `level` is specified this means the maximum nesting level
  that is shown. The value of `level` should be in the range 1..5, values outside
  this range are considered to be 5. In case no `level` is specified `level` is
  set to 5 (show all)
  In case no `option`. is specified \c \\tableofcontents acts as if just the
  `option` `HTML` and `XML` was specified. In case of multiple \c \\tableofcontents
  commands in a page the `option`(s) will be used additional to the already
  specified `option`(s), but only the last `level` of an `option` is valid.

  \warning This command only works inside related page documentation and
           \e not in other documentation blocks and only has effect in the
           the specified output!

<hr>
\section cmdsection \\section <section-name> (section title)

  \addindex \\section
  Creates a section with name \<section-name\>. The title of the
  section should be specified as the second argument of the \c \\section
  command.

  \warning This command only works inside related page documentation and
           \e not in other documentation blocks!

  \sa
   Section \ref cmdpage "\\page" for an example of the
           \c \\section command.

<hr>
\section cmdsubsection \\subsection <subsection-name> (subsection title)

  \addindex \\subsection
  Creates a subsection with name \<subsection-name\>. The title of the
  subsection should be specified as the second argument of the \c \\subsection
  command.

  \warning This command only works inside a section of a related page
           documentation block and
           \e not in other documentation blocks!

  \sa
   Section \ref cmdpage "\\page" for an example of the
           \c \\subsection command.

<hr>
\section cmdsubsubsection \\subsubsection <subsubsection-name> (subsubsection title)

  \addindex \\subsubsection
  Creates a subsubsection with name \<subsubsection-name\>. The title of the
  subsubsection should be specified as the second argument of the
  \c \\subsubsection command.

  \warning This command only works inside a subsection of a
           related page documentation block and
           \e not in other documentation blocks!

  \sa
   Section \ref cmdpage "\\page" for an example of the
           \ref cmdsection "\\section" command and
           \ref cmdsubsection "\\subsection" command.

<hr>
\section cmdparagraph \\paragraph <paragraph-name> (paragraph title)

  \addindex \\paragraph
  Creates a named paragraph with name \<paragraph-name\>. The title of the
  paragraph should be specified as the second argument of the
  \c \\paragraph command.

  \warning This command only works inside a subsubsection of a
           related page documentation block and
           \e not in other documentation blocks!

<hr>

\htmlonly</p><center><p>\endhtmlonly
<h2>
\htmlonly --- \endhtmlonly
Commands for displaying examples
\htmlonly --- \endhtmlonly
</h2>
\htmlonly</p></center><p>\endhtmlonly

<hr>
\section cmddontinclude \\dontinclude <file-name>

  \addindex \\dontinclude
  This command can be used to parse a source file without actually
  verbatim including it in the documentation (as the \ref cmdinclude "\\include" command does).
  This is useful if you want to divide the source file into smaller pieces and
  add documentation between the pieces.
  Source files or directories can be specified using the
  \ref cfg_example_path "EXAMPLE_PATH"
  tag of doxygen's configuration file.

  The class and member declarations and definitions inside the code fragment
  are 'remembered' during the parsing of the comment block that contained
  the \c \\dontinclude command.

  For line by line descriptions of source files, one or more lines
  of the example can be displayed using the \ref cmdline "\\line", 
  \ref cmdskip "\\skip", \ref cmdskipline "\\skipline", and
  \ref cmduntil "\\until" commands. An internal pointer is used for these commands. The
  \c \\dontinclude command sets the pointer to the first line of the example.

  \par Example:
  \include include.cpp
  Where the example file \c include_test.cpp looks as follows:
  \include include_test.cpp
  \htmlonly
  Click <a href="examples/include/html/example.html">here</a>
  for the corresponding HTML documentation that is generated by doxygen.
  \endhtmlonly
  \latexonly
  See \hyperlink{include_example}{Include example}
  for the corresponding \mbox{\LaTeX} documentation that is generated by doxygen.
  \endlatexonly

  \sa sections \ref cmdline "\\line", \ref cmdskip "\\skip",
               \ref cmdskipline "\\skipline", \ref cmduntil "\\until", and
               \ref cmdinclude "\\include".

</p><hr>
\section cmdinclude \\include[{lineno|doc}] <file-name>

  \addindex \\include
  This command can be used to include a source file as a block of code.
  The command takes the name of an include file as an argument.
  Source files or directories can be specified using the
  \ref cfg_example_path "EXAMPLE_PATH"
  tag of doxygen's configuration file.

  If \<file-name\> itself is not unique for the set of example files specified
  by the \ref cfg_example_path "EXAMPLE_PATH" tag, you can include part
  of the absolute path to disambiguate it.

  Using the \c \\include command is equivalent to inserting the file into
  the documentation block and surrounding it
  with \ref cmdcode "\\code" and \ref cmdendcode "\\endcode" commands.

  The main purpose of the \c \\include command is to avoid code
  duplication in case of example blocks that consist of multiple
  source and header files.

  For a line by line description of a source files use the
  \ref cmddontinclude "\\dontinclude" command in combination with
  the \ref cmdline "\\line", \ref cmdskip "\\skip",
  \ref cmdskipline "\\skipline",
  and \ref cmduntil "\\until" commands.

  Alternatively, the \ref cmdsnippet "\\snippet" command can be used to
  include only a fragment of a source file. For this to work the
  fragment has to be marked.

  \note Doxygen's special commands do not work inside blocks of code.
  It is allowed to nest C-style comments inside a code block though.

  You can add option `{lineno}` to enable line numbers for the included code if desired.

  You can add option `{doc}` to treat the file as documentation rather than code.

  \note Some that when using the `{doc}` option,
       commands like \ref cmdcond "\\cond" and \ref cmdif "\\if" don't work with
       this command due to the moment of parsing.

  \note The included documentation should not have comment signs in it as they will appear
       in the documentation as well.

  \sa sections \ref cmdexample "\\example", \ref cmddontinclude "\\dontinclude",
      \ref cmdverbatim "\\verbatim", \ref cmdincludedoc "\\includedoc", and
      \ref cmdsnippet "\\snippet".

<hr>
\section cmdincludelineno \\includelineno <file-name>

  \addindex \\includelineno
  This command is obsolete and is still supported for backward compatibility reasons,
  it works the same way as \ref cmdinclude "\\include{lineno}"

  \sa sections \ref cmdinclude "\\include{lineno}".

<hr>
\section cmdincludedoc \\includedoc <file-name>

  \addindex \\includedoc
  This command is obsolete and is still supported for backward compatibility reasons,
  it works the same way as \ref cmdinclude "\\include{doc}"

  \sa section \ref cmdinclude "\\include{doc}".

<hr>
\section cmdline \\line ( pattern )

  \addindex \\line
  This command searches line by line through the example that was last
  included using \ref cmdinclude "\\include" or
  \ref cmddontinclude "\\dontinclude" until it finds a non-blank
  line. If that line contains the specified pattern, it is written
  to the output.

  The internal pointer that is used to keep track of the current line in
  the example, is set to the start of the line following the non-blank
  line that was found (or to the end of the example if no such line could
  be found).

  See section \ref cmddontinclude "\\dontinclude" for an example.

<hr>
\section cmdskip \\skip ( pattern )

  \addindex \\skip
  This command searches line by line through the example that was last
  included using \ref cmdinclude "\\include" or
  \ref cmddontinclude "\\dontinclude" until it finds a line that contains
  the specified pattern.

  The internal pointer that is used to keep track of the current line in
  the example, is set to the start of the line that contains the specified
  pattern (or to the end of the example if the pattern could not be found).

  See section \ref cmddontinclude "\\dontinclude" for an example.

<hr>
\section cmdskipline \\skipline ( pattern )

  \addindex \\skipline
  This command searches line by line through the example that was last
  included using \ref cmdinclude "\\include" or
  \ref cmddontinclude "\\dontinclude" until it finds a line that contains
  the specified pattern. It then writes the line to the output.

  The internal pointer that is used to keep track of the current line in
  the example, is set to the start of the line following the line that is
  written (or to the end of the example if the pattern could not be found).

  \par Note:
    The command:
    \verbatim\skipline pattern\endverbatim
    is equivalent to:
\verbatim
\skip pattern
\line pattern\endverbatim

  See section \ref cmddontinclude "\\dontinclude" for an example.

<hr>
\section cmdsnippet \\snippet[{lineno|doc}] <file-name> ( block_id )

 \addindex \\snippet
 Where the \ref cmdinclude "\\include" command can be used to include
 a complete file as source code, this command can be used to quote only
 a fragment of a source file. In case `this` is used as <file-name> the
 current file is taken as file to take the snippet from.

 For example, the putting the following command in the documentation,
 references a snippet in file \c example.cpp residing in a subdirectory 
 which should be pointed to by \ref cfg_example_path "EXAMPLE_PATH".

\verbatim
  \snippet snippets/example.cpp Adding a resource
\endverbatim

 The text following the file name is the unique identifier for the snippet. 
 This is used to delimit the quoted code in the relevant snippet file as 
 shown in the following example that corresponds to the above \c \\snippet 
 command:

\code
    QImage image(64, 64, QImage::Format_RGB32);
    image.fill(qRgb(255, 160, 128));

//! [Adding a resource]
    document->addResource(QTextDocument::ImageResource,
        QUrl("mydata://image.png"), QVariant(image));
//! [Adding a resource]
    ...
\endcode

 Note that the lines containing the block markers will not be included,
 so the output will be:

\code
    document->addResource(QTextDocument::ImageResource,
        QUrl("mydata://image.png"), QVariant(image));
\endcode

 Note also that the [block_id] markers should appear exactly twice in the
 source file.

 You can add option `{lineno}` to enable line numbers for the snippet if desired.

 You can add option `{doc}` to treat the file as documentation rather than code.

 \note Some that when using the `{doc}` option,
       commands like \ref cmdcond "\\cond" and \ref cmdif "\\if" don't work with
       this command due to the moment of parsing.

 \note The included documentation should not have comment signs in it as they will appear
       in the documentation as well.

 see section \ref cmddontinclude "\\dontinclude" for an alternative way
 to include fragments of a source file that does not require markers.

<hr>
\section cmdsnippetlineno \\snippetlineno <file-name> ( block_id )

  \addindex \\snippetlineno
  This command is obsolete and is still supported for backward compatibility reasons,
  it works the same way as \ref cmdsnippet "\\snippet{lineno}"

  \sa sections \ref cmdsnippet "\\snippet{lineno}"

<hr>
\section cmdsnippetdoc \\snippetdoc <file-name> ( block_id )

  \addindex \\snippetdoc
  This command is obsolete and is still supported for backward compatibility reasons,
  it works the same way as \ref cmdsnippet "\\snippet{doc}"

  \sa section \ref cmdsnippet "\\snippet{doc}" and \ref cmdinclude "\\include{doc}".

<hr>
\section cmduntil \\until ( pattern )

  \addindex \\until
  This command writes all lines of the example that was last
  included using \ref cmdinclude "\\include" or
  \ref cmddontinclude "\\dontinclude"  to the output, until it finds
  a line containing the specified pattern. The line containing the pattern
  will be written as well.

  The internal pointer that is used to keep track of the current line in
  the example, is set to the start of the line following last written
  line (or to the end of the example if the pattern could not be found).

  See section \ref cmddontinclude "\\dontinclude" for an example.

<hr>
\section cmdverbinclude \\verbinclude <file-name>

  \addindex \\verbinclude
  This command includes the file \<file-name\> verbatim in the documentation.
  The command is equivalent to pasting the file in the documentation and
  placing \ref cmdverbatim "\\verbatim" and \ref cmdendverbatim "\\endverbatim"
  commands around it.

  Files or directories that doxygen should look for can be specified using the
  \ref cfg_example_path "EXAMPLE_PATH" tag of doxygen's configuration file.

<hr>
\section cmdhtmlinclude \\htmlinclude ["[block]"] <file-name>

  \addindex \\htmlinclude
  This command includes the file \<file-name\> as is in the HTML documentation.
  The command is equivalent to pasting the file in the documentation and
  placing \ref cmdhtmlonly "\\htmlonly" and \ref cmdendhtmlonly "\\endhtmlonly"
  commands around it.

  Normally the contents of the file indicated by \ref cmdhtmlinclude "\\htmlinclude"
  is inserted as-is. When you
  want to insert a HTML fragment that has block scope like a table or list
  which should appear outside \<p\>..\</p\>, this can lead to invalid HTML.
  You can use \\htmlinclude[block] to make doxygen
  end the current paragraph and restart after the file is included.

  Files or directories that doxygen should look for can be specified using the
  \ref cfg_example_path "EXAMPLE_PATH" tag of doxygen's configuration file.

  \sa section \ref cmdhtmlonly "\\htmlonly". 
<hr>

\section cmdlatexinclude \\latexinclude <file-name>

  \addindex \\latexinclude
  This command includes the file \<file-name\> as is in the \LaTeX documentation.
  The command is equivalent to pasting the file in the documentation and
  placing \ref cmdlatexonly "\\latexonly" and \ref cmdendlatexonly "\\endlatexonly"
  commands around it.

  Files or directories that doxygen should look for can be specified using the
  \ref cfg_example_path "EXAMPLE_PATH" tag of doxygen's configuration file.

<hr>

\htmlonly</p><center><p>\endhtmlonly
<h2>
\htmlonly --- \endhtmlonly
Commands for visual enhancements
\htmlonly --- \endhtmlonly
</h2>
\htmlonly</p></center><p>\endhtmlonly

\section cmda \\a <word>

  \addindex \\a
  Displays the argument \<word\> in italics.
  Use this command to emphasize words.
  Use this command to refer to member arguments in the running text.

  \par Example:
  \verbatim
  ... the \a x and \a y coordinates are used to ...
  \endverbatim
  This will result in the following text:<br><br>
  ... the \a x and \a y coordinates are used to ...

  Equivalent to \ref cmde "\\e" and \ref cmdem "\\em".
  To emphasize multiple words use \<em\>multiple words\</em\>.

<hr>
\section cmdarg \\arg { item-description }

  \addindex \\arg
  This command has one argument that continues until the first
  blank line or until another \c \\arg is encountered.
  The command can be used to generate a simple, not nested list of
  arguments.
  Each argument should start with a \c \\arg command.

  \par Example:
  Typing:
  \verbatim
  \arg \c AlignLeft left alignment.
  \arg \c AlignCenter center alignment.
  \arg \c AlignRight right alignment

  No other types of alignment are supported.
  \endverbatim
  will result in the following text:<br><br>
  <ul>
  <li> \c AlignLeft left alignment.
  <li> \c AlignCenter center alignment.
  <li> \c AlignRight right alignment
  </ul><br>
  No other types of alignment are supported.

  \par Note:
  For nested lists, HTML commands should be used.

  Equivalent to \ref cmdli "\\li"


<hr>
\section cmdb \\b <word>

  \addindex \\b
  Displays the argument \<word\> using a bold font.
  Equivalent to \<b\>word\</b\>.
  To put multiple words in bold use \<b\>multiple words\</b\>.

<hr>
\section cmdc \\c <word>

  \addindex \\c
  Displays the argument \<word\> using a typewriter font.
  Use this to refer to a word of code.
  Equivalent to \<tt\>word\</tt\>.

  \par Example:
  Typing:
  \verbatim
     ... This function returns \c void and not \c int ...
  \endverbatim
  will result in the following text:<br><br>
     ... This function returns \c void and not \c int ...

  Equivalent to \ref cmdp "\\p"
  To have multiple words in typewriter font use \<tt\>multiple words\</tt\>.

<hr>
\section cmdcode \\code [ '{'<word>'}']

  \addindex \\code
  Starts a block of code. A code block is treated differently
  from ordinary text. It is interpreted as source code. The names of 
  classes and members and other documented entities are automatically 
  replaced by links to the documentation.

  By default the language that is assumed for syntax highlighting is based
  on the location where the \c \\code block was found. If this part of
  a Python file for instance, the syntax highlight will be done according
  to the Python syntax. 

  If it unclear from the context which language is meant (for instance the
  comment is in a <code>.txt</code> or <code>.markdown</code> file) then you can also explicitly
  indicate the language, by putting the file extension typically
  that doxygen associated with the language in curly brackets after the
  code block. Here is an example:

\verbatim
  \code{.py}
  class Python:
     pass
  \endcode

  \code{.cpp}
  class Cpp {};
  \endcode
\endverbatim

  If the contents of the code block are in a language that doxygen cannot parse, doxygen
  will just show the output as-is. You can make this explicit using .unparsed, or by
  giving some other extension that doxygen doesn't support, e.g.

\verbatim
  \code{.unparsed}
  Show this as-is please
  \endcode

  \code{.sh}
  echo "This is a shell script"
  \endcode
\endverbatim

  \sa section \ref cmdendcode "\\endcode" and section \ref cmdverbatim "\\verbatim".

<hr>
\section cmdcopydoc \\copydoc <link-object>

  \addindex \\copydoc
  Copies a documentation block from the object specified by \<link-object\>
  and pastes it at the location of the command. This command can be useful
  to avoid cases where a documentation block would otherwise have to be
  duplicated or it can be used to extend the documentation of an inherited
  member.

  The link object can point to a member (of a class, file or group),
  a class, a namespace, a group, a page, or a file (checked in that order).
  Note that if the object pointed to is a member (function, variable,
  typedef, etc), the compound (class, file, or group) containing it
  should also be documented for the copying to work.

  To copy the documentation for a member of a
  class one can, for instance, put the following in the documentation:

\verbatim
  /*! @copydoc MyClass::myfunction()
   *  More documentation.
   */
\endverbatim

  if the member is overloaded, you should specify the argument types
  explicitly (without spaces!), like in the following:

\verbatim
  //! @copydoc MyClass::myfunction(type1,type2)
\endverbatim

  Qualified names are only needed if the context in which the documentation
  block is found requires them.

  The \c \\copydoc command can be used recursively, but cycles in the \c \\copydoc
  relation will be broken and flagged as an error.

  Note that <code>\\copydoc foo()</code> is roughly equivalent to doing:
\verbatim
  \brief \copybrief foo()
  \details \copydetails foo()
\endverbatim
  See \ref cmdcopybrief "\\copybrief" and
  \ref cmdcopydetails "\\copydetails" for copying only the brief or
  detailed part of the comment block.

<hr>
\section cmdcopybrief \\copybrief <link-object>

  \addindex \\copybrief
Works in a similar way as \ref cmdcopydoc "\\copydoc" but will
only copy the brief description, not the detailed documentation.

<hr>
\section cmdcopydetails \\copydetails <link-object>

  \addindex \\copydetails
Works in a similar way as \ref cmdcopydoc "\\copydoc" but will
only copy the detailed documentation, not the brief description.

<hr>
\section cmddocbookonly \\docbookonly

  \addindex \\docbookonly
  Starts a block of text that will be verbatim included in the
  generated DocBook documentation only. The block ends with a
  \ref cmdenddocbookonly "\\enddocbookonly" command.

  \sa section \ref cmdmanonly "\\manonly", 
              \ref cmdlatexonly "\\latexonly", 
              \ref cmdrtfonly "\\rtfonly", 
              \ref cmdxmlonly "\\xmlonly", and 
              \ref cmdhtmlonly "\\htmlonly".

<hr>
\section cmddot \\dot ["caption"] [<sizeindication>=<size>]

  \addindex \\dot
  Starts a text fragment which should contain a valid description of a
  dot graph. The text fragment ends with \ref cmdenddot "\\enddot".
  Doxygen will pass the text on to dot and include the resulting
  image (and image map) into the output.

  The first argument is optional and can be used to specify the caption
  that is displayed below the image. This argument has to be specified
  between quotes even if it does not contain any spaces. The quotes are
  stripped before the caption is displayed.

  The second argument is also optional and can be used to specify the
  width or height of the image.
  For a description of the possibilities see the paragraph
  \ref image_sizeindicator "Size indication" with the
  \ref cmdimage "\\image" command.

  The nodes of a graph can be made clickable by using the URL attribute.
  By using the command \ref cmdref "\\ref" inside the URL value you can conveniently
  link to an item inside doxygen. Here is an example:
\code
/*! class B */
class B {};

/*! class C */
class C {};

/*! \mainpage
 *
 *  Class relations expressed via an inline dot graph:
 *  \dot
 *  digraph example {
 *      node [shape=record, fontname=Helvetica, fontsize=10];
 *      b [ label="class B" URL="\ref B"];
 *      c [ label="class C" URL="\ref C"];
 *      b -> c [ arrowhead="open", style="dashed" ];
 *  }
 *  \enddot
 *  Note that the classes in the above graph are clickable
 *  (in the HTML output).
 */
\endcode

<hr>
\section cmdemoji \\emoji "name"

This command will produce an emoji character given its name.

The supported names are the ones also supported by GitHub and listed here
https://gist.github.com/rxaviers/7360908

You can use the name with or without colons, i.e.
`\emoji smile` is the same as writing `\emoji :smile:`.
When an emoji is not supported the name with by places in the
text with in between colons, i.e. `\emoji unsupported` will produce
`:unsupported:` in the output. Doxygen will also give a warning message.

See also the \ref emojisup "emoji support page" for details.

<hr>
\section cmdmsc \\msc ["caption"] [<sizeindication>=<size>]

  \addindex \\msc
  Starts a text fragment which should contain a valid description of a
  message sequence chart. See http://www.mcternan.me.uk/mscgen/ for examples.
  The text fragment ends with \ref cmdendmsc "\\endmsc".

  The first argument is optional and can be used to specify the caption
  that is displayed below the image. This argument has to be specified
  between quotes even if it does not contain any spaces. The quotes are
  stripped before the caption is displayed.

  The second argument is also optional and can be used to specify the
  width or height of the image. 
  For a description of the possibilities see the paragraph
  \ref image_sizeindicator "Size indication" with the
  \ref cmdimage "\\image" command.

  \note The text fragment should only include the part of the message
  sequence chart that is
  within the <code>msc {...}</code> block.
  \note You need to install the <code>mscgen</code> tool, if you want to use this
  command.

Here is an example of the use of the \c \\msc command.
\code
/** Sender class. Can be used to send a command to the server.
 *  The receiver will acknowledge the command by calling Ack().
 *  \msc
 *    Sender,Receiver;
 *    Sender->Receiver [label="Command()", URL="\ref Receiver::Command()"];
 *    Sender<-Receiver [label="Ack()", URL="\ref Ack()", ID="1"];
 *  \endmsc
 */
class Sender
{
  public:
    /** Acknowledgment from server */
    void Ack(bool ok);
};

/** Receiver class. Can be used to receive and execute commands.
 *  After execution of a command, the receiver will send an acknowledgment
 *  \msc
 *    Receiver,Sender;
 *    Receiver<-Sender [label="Command()", URL="\ref Command()"];
 *    Receiver->Sender [label="Ack()", URL="\ref Sender::Ack()", ID="1"];
 *  \endmsc
 */
class Receiver
{
  public:
    /** Executable a command on the server */
    void Command(int commandId);
};

\endcode

  \sa section \ref cmdmscfile "\\mscfile".

<hr>
\section cmdstartuml \\startuml [{file}] ["caption"] [<sizeindication>=<size>]

  \addindex \\startuml
  Starts a text fragment which should contain a valid description of a
  PlantUML diagram. See http://plantuml.com/ for examples.
  The text fragment ends with \ref cmdenduml "\\enduml".
  \note You need to install Java and the PlantUML's jar file,
  if you want to use this command. The location of the jar file should be specified
  using \ref cfg_plantuml_jar_path "PLANTUML_JAR_PATH".

  The first argument is optional and is for compatibility with running PlantUML as a preprocessing
  step before running doxygen, you can also add the name of the image file after \c \\startuml
  and inside curly brackets, i.e.
  \verbatim
  @startuml{myimage.png} "Image Caption" width=5cm
  Alice -> Bob : Hello
  @enduml
  \endverbatim
  When the name of the image is specified, doxygen will generate an image with that name.
  Without the name doxygen will choose a name automatically.

  The second argument is optional and can be used to specify the caption
  that is displayed below the image. This argument has to be specified
  between quotes even if it does not contain any spaces. The quotes are
  stripped before the caption is displayed.

  The third argument is also optional and can be used to specify the
  width or height of the image.
  For a description of the possibilities see the paragraph
  \ref image_sizeindicator "Size indication" with the
  \ref cmdimage "\\image" command.

Here is an example of the use of the \c \\startuml command.
\code
/** Sender class. Can be used to send a command to the server.
 *  The receiver will acknowledge the command by calling Ack().
 *  \startuml
 *    Sender->Receiver  : Command()
 *    Sender<--Receiver : Ack()
 *  \enduml
 */
class Sender
{
  public:
    /** Acknowledgment from server */
    void Ack(bool ok);
};

/** Receiver class. Can be used to receive and execute commands.
 *  After execution of a command, the receiver will send an acknowledgment
 *  \startuml
 *    Receiver<-Sender  : Command()
 *    Receiver-->Sender : Ack()
 *  \enduml
 */
class Receiver
{
  public:
    /** Executable a command on the server */
    void Command(int commandId);
};
\endcode

<hr>
\section cmddotfile \\dotfile <file> ["caption"] [<sizeindication>=<size>]

  \addindex \\dotfile
  Inserts an image generated by dot from \<file\> into the documentation.

  The first argument specifies the file name of the image.
  doxygen will look for files in the paths (or files) that you specified
  after the \ref cfg_dotfile_dirs "DOTFILE_DIRS" tag.
  If the dot file is found it will be used as an input file to the dot tool.
  The resulting image will be put into the correct output directory.
  If the dot file name contains spaces you'll have to put quotes ("...") around it.

  The second argument is optional and can be used to specify the caption
  that is displayed below the image. This argument has to be specified
  between quotes even if it does not contain any spaces. The quotes are
  stripped before the caption is displayed.

  The third argument is also optional and can be used to specify the
  width or height of the image.
  For a description of the possibilities see the paragraph
  \ref image_sizeindicator "Size indication" with the
  \ref cmdimage "\\image" command.

  \sa section \ref cmddot "\\dot".

<hr>
\section cmdmscfile \\mscfile <file> ["caption"] [<sizeindication>=<size>]

  \addindex \\mscfile
  Inserts an image generated by mscgen from \<file\> into the documentation.
  See http://www.mcternan.me.uk/mscgen/ for examples.

  The first argument specifies the file name of the image.
  doxygen will look for files in the paths (or files) that you specified
  after the \ref cfg_mscfile_dirs "MSCFILE_DIRS" tag.
  If the msc file is found it will be used as an input file to the mscgen tool.
  The resulting image will be put into the correct output directory.
  If the msc file name contains spaces you'll have to put quotes ("...") around it.

  The second argument is optional and can be used to specify the caption
  that is displayed below the image. This argument has to be specified
  between quotes even if it does not contain any spaces. The quotes are
  stripped before the caption is displayed.

  The third argument is also optional and can be used to specify the
  width or height of the image.
  For a description of the possibilities see the paragraph
  \ref image_sizeindicator "Size indication" with the
  \ref cmdimage "\\image" command.

  \sa section \ref cmdmsc "\\msc".

<hr>
\section cmddiafile \\diafile <file> ["caption"] [<sizeindication>=<size>]

  \addindex \\diafile
  Inserts an image made in dia from \<file\> into the documentation.

  The first argument specifies the file name of the image.
  doxygen will look for files in the paths (or files) that you specified
  after the \ref cfg_diafile_dirs "DIAFILE_DIRS" tag.
  If the dia file is found it will be used as an input file dia.
  The resulting image will be put into the correct output directory.
  If the dia file name contains spaces you'll have to put quotes ("...") around it.

  The second argument is optional and can be used to specify the caption
  that is displayed below the image. This argument has to be specified
  between quotes even if it does not contain any spaces. The quotes are
  stripped before the caption is displayed.

  The third argument is also optional and can be used to specify the
  width or height of the image.
  For a description of the possibilities see the paragraph
  \ref image_sizeindicator "Size indication" with the
  \ref cmdimage "\\image" command.

<hr>
\section cmde \\e <word>

  \addindex \\e
  Displays the argument \<word\> in italics.
  Use this command to emphasize words.

  \par Example:
  Typing:
  \verbatim
  ... this is a \e really good example ...
  \endverbatim
  will result in the following text:<br><br>
  ... this is a \e really good example ...

  Equivalent to \ref cmda "\\a" and \ref cmdem "\\em".
  To emphasize multiple words use \<em\>multiple words\</em\>.

<hr>
\section cmdem \\em <word>

  \addindex \\em
  Displays the argument \<word\> in italics.
  Use this command to emphasize words.

  \par Example:
  Typing:
  \verbatim
  ... this is a \em really good example ...
  \endverbatim
  will result in the following text:<br><br>
  ... this is a \em really good example ...

  Equivalent to \ref cmda "\\a" and \ref cmde "\\e".
  To emphasize multiple words use \<em\>multiple words\</em\>.

<hr>
\section cmdendcode \\endcode

  \addindex \\endcode
  Ends a block of code.
  \sa section \ref cmdcode "\\code"

<hr>
\section cmdenddocbookonly \\enddocbookonly

  \addindex \\enddocbookonly
  Ends a block of text that was started with a \ref cmddocbookonly "\\docbookonly" command.

  \sa section \ref cmddocbookonly "\\docbookonly".

<hr>
\section cmdenddot \\enddot

  \addindex \\enddot
  Ends a block that was started with \ref cmddot "\\dot".

<hr>
\section cmdendmsc \\endmsc

  \addindex \\endmsc
  Ends a block that was started with \ref cmdmsc "\\msc".

<hr>
\section cmdenduml \\enduml

  \addindex \\enduml
  Ends a block that was started with \ref cmdstartuml "\\startuml".

<hr>
\section cmdendhtmlonly \\endhtmlonly

  \addindex \\endhtmlonly
  Ends a block of text that was started with a \ref cmdhtmlonly "\\htmlonly" command.

  \sa section \ref cmdhtmlonly "\\htmlonly".

<hr>
\section cmdendlatexonly \\endlatexonly

  \addindex \\endlatexonly
  Ends a block of text that was started with a \ref cmdlatexonly "\\latexonly" command.

  \sa section \ref cmdlatexonly "\\latexonly".

<hr>
\section cmdendmanonly \\endmanonly

  \addindex \\endmanonly
  Ends a block of text that was started with a \ref cmdmanonly "\\manonly" command.

  \sa section \ref cmdmanonly "\\manonly".

<hr>
\section cmdendrtfonly \\endrtfonly

  \addindex \\endrtfonly
  Ends a block of text that was started with a \ref cmdrtfonly "\\rtfonly" command.

  \sa section \ref cmdrtfonly "\\rtfonly".


<hr>
\section cmdendverbatim \\endverbatim

  \addindex \\endverbatim
  Ends a block of text that was started with a \ref cmdverbatim "\\verbatim" command.

  \sa section \ref cmdverbatim "\\verbatim".

<hr>
\section cmdendxmlonly \\endxmlonly

  \addindex \\endxmlonly
  Ends a block of text that was started with a \ref cmdxmlonly "\\xmlonly" command.

  \sa section \ref cmdxmlonly "\\xmlonly".

<hr>
\section cmdfdollar \\f$

  \addindex \\f\$

  Marks the start and end of an in-text formula.
  \sa section \ref formulas "formulas" for an example.

<hr>
\section cmdfbropen \\f[

  \addindex \\f[

  Marks the start of a long formula that is displayed
  centered on a separate line.
  \sa section \ref cmdfbrclose "\\f]" and section \ref formulas "formulas".

<hr>
\section cmdfbrclose \\f]

  \addindex \\f]

  Marks the end of a long formula that is displayed
  centered on a separate line.
  \sa section \ref cmdfbropen "\\f[" and section \ref formulas "formulas".

<hr>
\section cmdfcurlyopen \\f{environment}{

  \addindex \\f{

  Marks the start of a formula that is in a specific environment.
  \note The second \c { is optional and is only to help editors (such as \c Vim) to
  do proper syntax highlighting by making the number of opening and closing braces
  the same.
  \sa section \ref cmdfcurlyclose "\\f}" and section \ref formulas "formulas".

<hr>
\section cmdfcurlyclose \\f}

  \addindex \\f}

  Marks the end of a formula that is in a specific environment.
  \sa section \ref cmdfcurlyopen "\\f{" and section \ref formulas "formulas".

<hr>
\section cmdhtmlonly \\htmlonly ["[block]"]

  \addindex \\htmlonly
  Starts a block of text that will be verbatim included in the
  generated HTML documentation only. The block ends with a
  \ref cmdendhtmlonly "\\endhtmlonly" command.

  This command can be used to include HTML code that is too complex
  for doxygen (i.e. applets, java-scripts, and HTML tags that
  require specific attributes).

  Normally the contents between \ref cmdhtmlonly "\\htmlonly" and
  \ref cmdendhtmlonly "\\endhtmlonly" is inserted as-is. When you
  want to insert a HTML fragment that has block scope like a table or list
  which should appear outside \<p\>..\</p\>, this can lead to invalid HTML.
  You can use \\htmlonly[block] to make doxygen
  end the current paragraph and restart it after \\endhtmlonly.

  \note environment variables (like \$(HOME) ) are resolved inside a
  HTML-only block.

  \sa section \ref cmdmanonly "\\manonly", 
              \ref cmdlatexonly "\\latexonly", 
              \ref cmdrtfonly "\\rtfonly", 
              \ref cmdxmlonly "\\xmlonly",
              \ref cmddocbookonly "\\docbookonly", and
              \ref cmdhtmlinclude "\\htmlinclude".

<hr>
\section cmdimage \\image['{'[option]'}'] <format> <file> ["caption"] [<sizeindication>=<size>]

  \addindex \\image
  Inserts an image into the documentation. This command is format
  specific, so if you want to insert an image for more than one
  format you'll have to repeat this command for each format.

  The first argument specifies the output format in which the image should
  be embedded. Currently, the following values are supported:
  \c html, \c latex, \c docbook and \c rtf.

  The second argument specifies the file name of the image.
  doxygen will look for files in the paths (or files) that you specified
  after the \ref cfg_image_path "IMAGE_PATH" tag.
  If the image is found it will be copied to the correct output directory.
  If the image name contains spaces you'll have to put quotes ("...") around
  the name. You can also specify an absolute URL instead of a file name, but then
  doxygen does not copy the image nor check its existence.

  The third argument is optional and can be used to specify the caption
  that is displayed below the image. This argument has to be specified
  on a single line and between quotes even if it does not contain any
  spaces. The quotes are stripped before the caption is displayed.

  The fourth argument is also optional and can be used to specify the
  width or height of the image. This can be useful for \LaTeX or DocBook output
  (i.e. format=<code>latex</code> or format=<code>docbook</code>).
  \anchor image_sizeindicator \par Size indication
  The \c sizeindication can specify the width or height to be used (or a combination).
  The size specifier in \LaTeX (for example `10cm` or
  `4in` or a symbolic width like `\\textwidth`).

  Currently only the option `inline` is supported. In case the option `inline` is
  specified the image is placed "in the line", when a caption s present it is shown 
  in HTML as tooltip (ignored for the other formats).

  Here is example of a comment block:

\verbatim
  /*! Here is a snapshot of my new application:
   *  \image html application.jpg
   *  \image latex application.eps "My application" width=10cm
   */
\endverbatim

  And this is an example of how the relevant part of the configuration file
  may look:

\verbatim
  IMAGE_PATH     = my_image_dir
\endverbatim

  \warning The image format for HTML is limited to what your
           browser supports. For \LaTeX, the image format
           must be Encapsulated PostScript (eps).
           <br><br>
           Doxygen does not check if the image is in the correct format.
           So \e you have to make sure this is the case!

<hr>
\section cmdlatexonly \\latexonly

  \addindex \\latexonly
  Starts a block of text that will be verbatim included in the
  generated \LaTeX documentation only. The block ends with a
  \ref cmdendlatexonly "\\endlatexonly" command.

  This command can be used to include \LaTeX code that is too
  complex for doxygen (i.e. images, formulas, special characters). You can
  use the \ref cmdhtmlonly "\\htmlonly" and \ref cmdendhtmlonly "\\endhtmlonly"
  pair to provide a proper HTML alternative.

  \b Note:
    environment variables (like \$(HOME) ) are resolved inside a
    \LaTeX-only block.

  \sa sections \ref cmdrtfonly "\\rtfonly",
               \ref cmdxmlonly "\\xmlonly",
               \ref cmdmanonly "\\manonly",
               \ref cmdhtmlonly "\\htmlonly", and
               \ref cmdhtmlonly "\\docbookonly".

<hr>
\section cmdmanonly \\manonly

  \addindex \\manonly
  Starts a block of text that will be verbatim included in the
  generated MAN documentation only. The block ends with a
  \ref cmdendmanonly "\\endmanonly" command.

  This command can be used to include groff code directly into
  MAN pages. You can use the \ref cmdhtmlonly "\\htmlonly" and
  \ref cmdendhtmlonly "\\endhtmlonly" and
  \ref cmdlatexonly "\\latexonly" and
  \ref cmdendlatexonly "\\endlatexonly" pairs to provide proper
  HTML and \LaTeX alternatives.

  \sa sections \ref cmdhtmlonly "\\htmlonly",
               \ref cmdxmlonly "\\xmlonly",
               \ref cmdrtfonly "\\rtfonly",
               \ref cmdlatexonly "\\latexonly", and
               \ref cmddocbookonly "\\docbookonly".

<hr>
\section cmdli \\li { item-description }

  \addindex \\li
  This command has one argument that continues until the first
  blank line or until another \c \\li is encountered.
  The command can be used to generate a simple, not nested list of
  arguments.
  Each argument should start with a \c \\li command.

  \par Example:
  Typing:
  \verbatim
  \li \c AlignLeft left alignment.
  \li \c AlignCenter center alignment.
  \li \c AlignRight right alignment

  No other types of alignment are supported.
  \endverbatim
  will result in the following text:<br><br>
  <ul>
  <li> \c AlignLeft left alignment.
  <li> \c AlignCenter center alignment.
  <li> \c AlignRight right alignment
  </ul><br>
  No other types of alignment are supported.

  \par Note:
  For nested lists, HTML commands should be used.

  Equivalent to \ref cmdarg "\\arg"

<hr>
\section cmdn \\n

  \addindex \\n
  Forces a new line. Equivalent to \<br\> and inspired by
  the \c printf function.

<hr>
\section cmdp \\p <word>

  \addindex \\p
  Displays the parameter \<word\> using a typewriter font.
  You can use this command to refer to member function parameters in
  the running text.

  \par Example:
  \verbatim
  ... the \p x and \p y coordinates are used to ...
  \endverbatim
  This will result in the following text:<br><br>
  ... the \p x and \p y coordinates are used to ...

  Equivalent to \ref cmdc "\\c"
  To have multiple words in typewriter font use \<tt\>multiple words\</tt\>.

<hr>
\section cmdrtfonly \\rtfonly

  \addindex \\rtfonly
  Starts a block of text that will be verbatim included in the
  generated RTF documentation only. The block ends with a
  \ref cmdendrtfonly "\\endrtfonly" command.

  This command can be used to include RTF code that is too complex
  for doxygen.

  \b Note:
    environment variables (like \$(HOME) ) are resolved inside a
    RTF-only block.

  \sa sections \ref cmdmanonly "\\manonly",
               \ref cmdxmlonly "\\xmlonly",
               \ref cmdlatexonly "\\latexonly",
               \ref cmdhtmlonly "\\htmlonly", and
               \ref cmddocbookonly "\\docbookonly".

<hr>
\section cmdverbatim \\verbatim

  \addindex \\verbatim
  Starts a block of text that will be verbatim included in
  the documentation. The block should end with a
  \ref cmdendverbatim "\\endverbatim" command.
  All commands are disabled in a verbatim block.

  \warning Make sure you include a \ref cmdendverbatim "\\endverbatim" command for each
  \c \\verbatim command or the parser will get confused!

  \sa sections \ref cmdcode "\\code",
               \ref cmdendverbatim "\\endverbatim" and
               \ref cmdverbinclude "\\verbinclude".

<hr>
\section cmdxmlonly \\xmlonly

  \addindex \\xmlonly
  Starts a block of text that will be verbatim included in the
  generated XML output only. The block ends with a
  \ref cmdendxmlonly "\\endxmlonly" command.

  This command can be used to include custom XML tags.

  \sa sections \ref cmdmanonly "\\manonly",
               \ref cmdrtfonly "\\rtfonly",
               \ref cmdlatexonly "\\latexonly",
               \ref cmdhtmlonly "\\htmlonly", and
               \ref cmddocbookonly "\\docbookonly".

<hr>
\section cmdbackslash \\\\

  \addindex \\\\
  This command writes a backslash character (\c \\) to the
  output. The backslash has to be escaped in some
  cases because doxygen uses it to detect commands.

<hr>
\section cmdat \\\@

  \addindex \\\@
  This command writes an at-sign (\c \@) to the output.
  The at-sign has to be escaped in some cases
  because doxygen uses it to detect Javadoc commands.

<hr>
\section cmdtilde \\~[LanguageId]
  \addindex \\~
  This command enables/disables a language specific filter. This can be
  used to put documentation for different language into one comment block
  and use the \ref cfg_output_language "OUTPUT_LANGUAGE" tag to filter out only a specific language.
  Use \c \\~language_id to enable output for a specific language only and
  \c \\~ to enable output for all languages (this is also the default mode).

  Example:
\verbatim
/*! \~english This is English \~dutch Dit is Nederlands \~german Dies ist
    Deutsch. \~ output for all languages.
 */
\endverbatim


<hr>
\section cmdamp \\\&

  \addindex \\\&
  This command writes the \c \& character to the output.
  This character has to be escaped because it has a special meaning in HTML.

<hr>
\section cmddollar \\\$

  \addindex \\\$
  This command writes the \c \$ character to the output.
  This character has to be escaped in some cases, because it is used to expand
  environment variables.

<hr>
\section cmdhash \\\#

  \addindex \\\#
  This command writes the \c \# character to the output. This
  character has to be escaped in some cases, because it is used to refer
  to documented entities.

<hr>
\section cmdlt \\\<

  \addindex \\\<
  This command writes the \c \< character to the output.
  This character has to be escaped because it has a special meaning in HTML.

<hr>
\section cmdgt \\\>

  \addindex \\\>
  This command writes the \c \> character to the output. This
  character has to be escaped because it has a special meaning in HTML.

<hr>
\section cmdperc \\\%

  \addindex \\\%
  This command writes the \c \% character to the output. This
  character has to be escaped in some cases, because it is used to
  prevent auto-linking to a word that is also a documented class or struct.

<hr>
\section cmdquot \\"

  \addindex \\\"
  This command writes the \c \" character to the output. This
  character has to be escaped in some cases, because it is used in pairs
  to indicate an unformatted text fragment.

<hr>
\section cmdchardot \\.

  \addindex \\\.
  This command writes a dot (`.`) to the output. This can be useful to 
  prevent ending a brief description when \ref cfg_javadoc_autobrief "JAVADOC_AUTOBRIEF" is enabled
  or to prevent starting a numbered list when the dot follows a number at
  the start of a line.

<hr>
\section cmddcolon \\::

  \addindex \\::
  This command writes a double colon (\c \::) to the output. This
  character sequence has to be escaped in some cases, because it is used
  to reference to documented entities.

<hr>
\section cmdpipe \\|

  \addindex \\|
  This command writes a pipe symbol (\|) to the output. This
  character has to be escaped in some cases, because it is used
  for Markdown tables.

<hr>
\section cmdndash \\--

  \addindex \\\--
  This command writes two dashes (\--) to the output. This allows
  writing two consecutive dashes to the output instead of one n-dash character (--).

<hr>
\section cmdmdash \\---

  \addindex \\\---
  This command writes three dashes (\---) to the output. This allows
  writing three consecutive dashes to the output instead of one m-dash character (---).

<hr>
\htmlonly</p><center><p>\endhtmlonly
<h2>
\htmlonly --- \endhtmlonly
Commands included for Qt compatibility
\htmlonly --- \endhtmlonly
</h2>
\htmlonly</p></center><p>\endhtmlonly

The following commands are supported to remain compatible to the Qt class
browser generator. Do \e not use these commands in your own documentation.
<ul>
<li>\\annotatedclasslist
<li>\\classhierarchy
<li>\\define
<li>\\functionindex
<li>\\header
<li>\\headerfilelist
<li>\\inherit
<li>\\l
<li>\\postheader
</ul>
<hr>


\htmlonly
</p>
Go to the <a href="htmlcmds.html">next</a> section or return to the
 <a href="index.html">index</a>.
<p>
\endhtmlonly

*/