quality/analysis? –Code Analysis: CI – https://www.sonarsource.com https://rules.sonarsource.com/cpp • Linter 549 rules • CI/CD integration • Code reviews • PR decorations https://www.jetbrains https://rules.sonarsource.com/cpp/tag/misra-c++2008 (51 rules) ● https://rules.sonarsource.com/cpp/tag/misra-c2004 (14 rules) ● https://rules.sonarsource.com/cpp/tag/misra-c2012 (10 rules) ● PVS-Studio Style ○ Formatting, Naming, Syntax style, …Formatting – ● ClangFormat ○ Formatting standard in C++ nowadays ○ Breaking compatibility ○ Fuzzy parsingNaming – ● Naming ○ camelCase, PascalCase

CMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class You don’t need to follow Note Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should related_name field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased

CMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class You don’t need to follow Note Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should related_name field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased

CMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: • PollPluginModel: the model class • PollPluginPublisher: the plugin class You don’t need to Note: Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should related_name field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased

CMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: • PollPluginModel: the model class • PollPluginPublisher: the plugin class You don’t need to Note: Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should related_name field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased

must have a name: The name should describe ‘what’ the function is doing at a minimum Some naming rules: ● Functions names must start with a letter or underscore. ● Note: ‘Usually’ names that begin described by the function name. Local variables declared in the function body follow normal scoping rules. Notes on function body: ● Later on we’ll see that the function body usually is defined in a source better C++ approach is to group functions together in a namespace ○ This makes it easy to avoid naming collisions ■ (Someone else probably wrote an ‘add’ function at some point in a large enough project)

CMSPluginBase and must register them- selves with the cms.plugin_pool.plugin_pool. The convention for plugin naming is as follows: • SomePlugin: the model class • CMSSomePlugin: the plugin class You don’t need to approriate related_name field that is now available on the Page object. As per the normal related_name naming mechanism, the appropriate field to access is the same as your Page- Extension model name, but lowercased with this menu item, primarily to follow naming conven- tion asserted by Django. get_menu_title() Utility method to return the associated title, using the same naming convention used by cms.models.pagemodel

communicates its purpose. Relies on both the syntax of the programming language and the quality of naming conventions.Syntax Evolution C++ 98: C++ 11: static const int arr[] = {1,2,3,4}; vector v(arr metafunctions::get<_STR("times4")> times4;Boost Metaparse - Grammar Create a parser from grammar rules typedef grammar<_STR("plus_exp")> ::rule<_STR("int ::= ('0'|'1'|'2'|...|'9')+"), int_action>::type As...>) -> list; auto pop_front(empty_list) -> empty_list;CTRE – LL(1) Parser The grammar rules lookup table is implemented as empty structs and function overloads struct pcre { struct backslash{};

CMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class A second convention is Note Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should related_name field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased

CMSPluginBase and must register themselves with the plugin_pool. A reasonable convention for plugin naming is: PollPluginModel: the model class PollPluginPublisher: the plugin class A second convention is Note Up to version 3.1 this module was named menu.py. Please update your existing modules to the new naming convention. Support for the old name will be removed in version 3.5. If you refresh a page you should related_name field that is now available on the Page object. Page extensions As per the normal related_name naming mechanism, the appropriate field to access is the same as your PageExtension model name, but lowercased