-
Notifications
You must be signed in to change notification settings - Fork 3
/
.astylerc
41 lines (40 loc) · 1.47 KB
/
.astylerc
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
# Astyle options for the riss toolbox
# -----------------------------------
#
# Inline comments over multiple lines, like:
#
# vec<Lit> conflict; // If problem is unsatisfiable (possibly under assumptions),
# // this vector represent the final conflict clause expressed in the assumptions.
#
# will be adjusted to:
#
# vec<Lit> conflict; // If problem is unsatisfiable (possibly under assumptions),
# // this vector represent the final conflict clause expressed in the assumptions.
#
# You have to fix it manually. If we would use multline comments (/* ... */ ) astylic would
# do it right. But for this we have to adjust all other comments for sake of consistency.
--style=k&r
# Pythons indention syntax is cool -- but not in C++ code. We use brackets for each
# statement.
--add-brackets
# indent class visibility modifiers (public, protected)
# one half indent
--indent-modifiers
--indent-labels
--indent-preproc-block
--indent-preproc-cond
--indent-preproc-define
--convert-tabs
# insert space padding around operators
--pad-oper
# Insert space padding between a header (e.g. 'if', 'for', 'while'...) and the following paren
--pad-header
# Remove extra space padding around parenthesis on the inside and outside
--unpad-paren
# riss and co. have a lot of one line statements.
# We keep them alive
--keep-one-line-statements
--keep-one-line-blocks
# The reference "&" will be written directly after the
# type
--align-reference=type