ALICE O2 C++ coding conventions
Adriana Telesca on behalf of the CWG2
March, 21st 2014
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community
Ask the community for help and clear up your study doubts
University Rankings
Discover the best universities in your country according to Docsity users
Free resources
Our save-the-student-ebooks!
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
ALICE O2 C++ Coding Conventions: Uniformity through Guidelines, Exercises of Communication
The ALICE O2 C++ coding conventions proposed by the CWG2 group in March 2014. The purpose of these conventions is to ensure uniformity in coding practices for the O2 software project, which involves contributions from various coders with different backgrounds. coding style, naming, formatting, and comments, with references to detailed guidelines available online.
What you will learn
- What are the reasons behind the creation of ALICE O2 C++ coding conventions?
- What are the key differences between the ALICE O2 C++ coding conventions and Google's C++ coding guidelines?
- Which guidelines were used as a starting point for the ALICE O2 C++ coding conventions?
- How does the document address the issue of different coding conventions among contributors?
Typology: Exercises
2021/2022
1 / 27
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download ALICE O2 C++ Coding Conventions: Uniformity through Guidelines and more Exercises Communication in PDF only on Docsity!
ALICE O^2 C++ coding conventions
Adriana Telesca on behalf of the CWG
March, 21st^2014
CWG
▶ Propose common guidelines, policies and procedures ▶ Conduct surveys for tools that cover the activities of most of the other working groups (aka Support tools) ▶ Coordinate other surveys ▶ Act as a central point where we keep track of who is evaluating what ▶ Ensure that resources are optimized and communication among the working groups is facilitated
Tools, guidelines and procedures
ALICE O^2 C++ coding conventions: why?
▶ O^2 as a fresh start
▶ However, contributions from many coders used to
different conventions
▶ Need to ensure uniformity
▶ Need to adopt common conventions
ALICE O^2 C++ coding conventions: decision
▶ Google C++ coding guidelines as starting point ▶ Widely used conventions taken into account ▶ Herb Sutter and Stroustrup’s guidelines considered ▶ C++11 features
▶ Big effort invested The result is different from both Google and AliRoot
Coding style
Goal
Coding style
Naming and formatting
Code style
Naming: General
Code style
Naming: Files
Code style
Naming: Functions
Coding style
Formatting: Line length and classes
Coding guidelines
Coding guidelines
▶ Namespaces:
▶ General and std
▶ Scoping:
▶ Variables and Brace initialization ▶ Global variables
▶ Classes:
▶ Initialization
▶ Others:
▶ Exceptions
Highlights
Coding guidelines
Namespaces: using declarations and directives
Coding guidelines
Scoping