|
2 months ago | |
---|---|---|
src | 2 months ago | |
test | 2 months ago | |
.clang-format | 2 months ago | |
.clang-tidy | 2 months ago | |
.gitignore | 2 months ago | |
LICENSE | 2 months ago | |
Makefile | 2 months ago | |
Makefile.conf | 2 months ago | |
README.md | 2 months ago | |
local.conf.example | 2 months ago |
Repository: REPO url here
Change management: JIRA url here
Doc: Wiki link here
Maintainer: e-mail here
Build-maintainers:
Please add here the technical requirements of the project
implementation: .cc
header: .hh
template-implementation: .hxx
all pEp source code must be in a top level namespace pEp
.
With this exception all other nested namespaces must be in CamelCase.
it is never encouraged to do use namespace std;
. In header files it is actually forbidden, and in implementation files it is
stronly discouraged, because as soon as you want to templatize, the using namespace
directive has to be replaced with explicit std::
prefixes,
because the templateized implementation will have to be in a header file extension (.hxx)
This applies strongly for the namespace std
and needs to be carefully considered for all other namespaces.
Do not use #pragma once , use #ifdef/#define style (portability reasons)
naming key: PROJECTNAME_FILENAME (e.g. LIBPEPDATATYPES_FILENAME_HH
)