Skip to content
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.

Coding Style

darioizzo edited this page Nov 19, 2014 · 5 revisions

C++

Though we are not as 'rigid' as the original post, we do force the Linux Kernel coding guidelines to all developers. Even if PaGMO is written in C++, most of those rules do apply. For those that do not, please find in the already existing code an example of what you are trying to write and stick to its formatting. Do not invent new conventions. Ever.

There is only one golden rule in PaGMO, one with NO EXCEPTIONS. We call this the Biscani rule :"THOU SHALL NOT USE delete IN ANY PART OF PaGMO". If you think you need delete, then you should immediately stop coding and go back to agriculture.

Python

We use the PEP8 coding conventions with soft-tabs of 4 spaces. Please use a tool like to pep8 or autopep8 to check your code before committing or issuing a pull request.

Clone this wiki locally