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
|
const char *bar;
typedef
(const char *)
(Taj::GlobalType, Hi& *) foo;
int sillyVar = 1;
enum Test::FuBar { Test1 = 1, // Test
Test2, // Also a test
Test3,
Test4 = 4
};
/* gringrin
* multi
* line \
comment
*/
#include<taj.h>
#define MY_DEF 1
const char *FuBar( const char *str = "dog", int, 2 )const;
/**
* Doc
* Documentation.
*
* What does it mean to write class documentation? Is it something naughty?
*
* Is it something nice?
* @li Maybe
* @li Maybe not. Maybe if we wrote lots of text here, it would make it into
* the list we have got here.
* @li Perhaps.
*
* Or should it be something that we'll never ever do if we're sober? After
* all, sobriety is the vice of strife.
*
* @li another
* @li list
*
* @see Taj
*
* @author Taj
* @version Break
*/
template <class T, // Comment
basic_string<T<TWibble>, 2>>
class TWibble
:
public normal,
protected templated<T>
{
/**
* I believe that I have documentation, and you don't.
*/
virtual const char *retthis(
(TWibble *), // A pointer thing
Test *(test) ); // another one
struct MyClass {
int a;
int b;
const char *c;
void init( int, int, const char * );
};
/** @return a small dog. */
const char *doggie() const;
protected:
/**
* Stufff
*/
int _myVar;
public slots:
const char *dontRet() const = 0;
}; /* end of class */
const char *MyVar;
|
