|
Size: 1193
Comment:
|
Size: 1449
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| * [[/Includes]]: using {{{include-what-you-use}}} to find missing/redundant includes and forward declarations | |
| Line 15: | Line 16: |
| * [[/CodeBasesToMerge]]: Code from papers we want to merge in the (medium-term) future | * [[/CodeBasesToMerge]]: code from papers we want to merge in the (medium-term) future * [[/ProblemTransformations]]: problem transformations performed by the planner that might trip up users interested in non-classical planning |
Back to the HomePage.
Information for developers
Subpages:
/Mercurial: our Mercurial workflow and Mercurial tips and tricks
/CodingConventions: coding conventions for C++ code
/Whitespace: how to indent, where to break lines, where to put spaces etc. in C++ code
/Uncrustify: using the uncrustify source code pretty printer, including integration with Mercurial
/Includes: using include-what-you-use to find missing/redundant includes and forward declarations
/CodeReview: how to use the Rietveld code review tool with our codebase
/GkiGrid: how to run experiments on the GKI grid
/BuildBot: buildbot information
/ImplementationDetails: more in-depth descriptions on how some classes are implemented
/CodeBasesToMerge: code from papers we want to merge in the (medium-term) future
/ProblemTransformations: problem transformations performed by the planner that might trip up users interested in non-classical planning
Other bits and pieces
Mailing lists: Core developers, please subscribe to both the public and the internal mailing lists mentioned on the HomePage.
Admin interface to the internal mailing list: https://lists.informatik.uni-freiburg.de/mailman/admin/downward-dev
Python code: We follow PEP 8 and support Python 2.7 and Python >= 3.2.