13
13
https://launchpad.net/vqdr
23
24
DICE EXPRESSION SYNTAX
25
A dice expression is simple.
28
[n]d[m], [n]t[m] - [n] dices with [m] sides.
29
[e1] [op] [e2] - Use operator [op] on expressions [e1] and [e2]
31
[func]([e...]) - Use function [func] on the expression(s) [e...]
26
A dice expression is simple.
29
[n]d[m], [n]t[m] - [n] dices with [m] sides.
30
[e1] [op] [e2] - Use operator [op] on expressions [e1] and [e2]
32
[func]([e...]) - Use function [func] on the expression(s) [e...]
35
HACKING (DEVELOPMENT GUIDELINES)
37
Please use stardard vala naming convetion. This to make it as easy to read as
38
passible, and minimise any errors when interating with other libraries.
42
Always use two spaces for indentation detween levels.
46
Use int[n] types instead of int and long. This to guarentee that the
47
behviour is the same on all platforms.
51
All type names should start with a capital letter, and each word in the name
52
should start with a capital letter. No seperation should be made between
53
the words in the name.
56
class ClownFactory {...}
61
Function and method namse should has the standard naming convetion of vala:
64
void foo_bar (int something);
67
* There should be a space befor the paranthesis.
68
* Use underlines to seperate words in the function name.
70
It is advicable to have the function names as short as possible, but also
71
descriptive. Sometimes this leads to a copromise between readability, and
76
When defining variables use underlines between words:
84
When defining enums, make sure that the 0'th value is invalid, this to avoid
85
any potential NULL traps.
87
Always define a last value named _NUM_VAL, this will be used for validation
101
It is advicable to define a to_string method for the enums. To keep track
102
of the to_string functions cases, it is advicable to add a static assert
103
to the body of the function to catch problems at compile time.
110
public string to_string () {
111
static_assert (Clowns._NUM_VAL = 4 + 1);
119
assert_not_reached ();