The rules and advices are for everybody. In every environment and situation there will always be suggestions and norms that will keep order and sense in every possible ways.<\/p>\n

In high level programming languages is absolutely the same, there are several conditions that help guiding the user while he is developing an application or a program, the only exception is that we don\u2019t call them as \u201cRules\u201d, instead, we know them as Code Conventions<\/strong> and of course, every programming language has different conventions to follow, they may look alike in some aspects but believe me when I tell you that the differences can also be huge.<\/p>\n

In this mastery we are going to check out the Code conventions of C++. <\/strong>Outstanding the most important aspects of this rules so you can improve your skills programming and of course, following the right way to do it.<\/p>\n

Microsoft defines \u201cCoding Conventions<\/strong>\u201d as following:<\/p>\n

Coding conventions are suggestions that may help you write in a specific programming language.<\/p>\n

Coding conventions can include the following:<\/p>\n

\n
• Naming conventions for objects, variables, and procedures<\/li>\n
• Commenting conventions<\/li>\n
• Text formatting and indenting guidelines<\/li>\n<\/ul>\n

  The main reason for using a consistent set of coding conventions is to standardize the structure and coding style of a script or set of scripts so that you and others can easily read and understand the code. Using good coding conventions results in precise, readable, and unambiguous source code that is consistent with other language conventions and as intuitive as possible.<\/p>\n

  We can make a list of the main aspects about the coding conventions, including the most important aspects, such as:<\/p>\n

  \n
  • General Recommendations.<\/li>\n
  • Naming conventions.<\/li>\n
  • Files<\/li>\n
  • Statements<\/li>\n<\/ul>\n

    \u00a0<\/em><\/strong><\/p>\n

    GENERAL RECOMMENDATIONS.<\/em><\/strong><\/p>\n

    \n
    1. Any violation to the guide is allowed if it enhances readability.<\/u><\/li>\n<\/ol>\n

       The main goal of the recommendation is to improve readability and thereby the understanding and the maintainability and general quality of the code.<\/p>\n

       \n
       1. The rules can be violated if there are strong personal objections against them.<\/u><\/li>\n<\/ol>\n

          The attempt is to make a guideline, not to force a particular coding style onto individuals.<\/p>\n

          NAMING CONVENTIONS.<\/em><\/strong><\/p>\n

          \n
          1. Names representing types must be in mixed case starting with upper case.<\/u><\/li>\n<\/ol>\n
             \n
             1. Variable names must be in mixed case starting with lower case.<\/u><\/li>\n<\/ol>\n
                \n
                1. Named constants (including enumeration values) must be all uppercase using underscore to separate words.<\/u><\/li>\n<\/ol>\n
                   \n
                   1. Names representing methods or functions must be verbs and written in mixed case starting with lower case.<\/u><\/li>\n<\/ol>\n
                      \n
                      1. All names should be written in English.<\/u><\/li>\n<\/ol>\n
                         \n
                         1. The prefix n should be used for variables representing a number of objects.<\/u><\/li>\n<\/ol>\n
                            \n
                            1. Abbreviations in names should be avoided.<\/u><\/li>\n<\/ol>\n
                               \n
                               1. Functions (methods returning something) should be named after what they return and procedures (void methods) after what they do.<\/u><\/li>\n<\/ol>\n

                                  FILES.<\/em><\/strong><\/p>\n

                                  \n
                                  1. C++ header files should have the extension .h (preferred) or .hpp. Source files can have the extension .c++ (recommended), .C, .cc or .cpp<\/li>\n<\/ol>\n
                                     \n
                                     1. A class should be declared in a header file and defined in a source file where the name of the files match the name of the class.<\/li>\n<\/ol>\n
                                        \n
                                        1. All definitions should reside in source files.<\/li>\n<\/ol>\n
                                           \n
                                           1. File content must be kept within 80 columns.<\/li>\n<\/ol>\n
                                              \n
                                              1. Special characters like TAB and page break must be avoided.<\/li>\n<\/ol>\n
                                                 \n
                                                 1. Header files must contain an include guard.<\/li>\n<\/ol>\n
                                                    \n
                                                    1. The incompleteness of split lines must be made obvious.<\/li>\n<\/ol>\n

                                                       STATEMENTS.<\/em><\/strong><\/p>\n

                                                       \n
                                                       1. Types that are local to one file only can be declared inside that file.<\/li>\n<\/ol>\n
                                                          \n
                                                          1. Variables should be initialized where they are declared.<\/li>\n<\/ol>\n
                                                             \n
                                                             1. C++ pointers and references should have their reference symbol next to the type rather than to the name.<\/li>\n<\/ol>\n
                                                                \n
                                                                1. Loop variables should be initialized immediately before the loop.<\/li>\n<\/ol>\n
                                                                   \n
                                                                   1. The form while(true) should be used for infinite loops.<\/li>\n<\/ol>\n
                                                                      \n
                                                                      1. Complex conditional expressions must be avoided. Introduce temporary Boolean variables instead.<\/li>\n<\/ol>\n

                                                                         Those were some of the most important conventions used for C++ divided by categories. Therefore it is really important to memorize as much as we can so we can improve our programming skills and make our code syntaxes even clearer so everyone with knowledge of the language will be able to understand it without problems.<\/p>\n

                                                                         Here<\/a> is a page where you will be able to see all the Code Convention of C++ and some really good examples.<\/p>\n

                                                                         <\/a> <\/p>\n","protected":false},"excerpt":{"rendered":"

                                                                         The rules and advices are for everybody. In every environment and situation there will always be suggestions and norms that will keep order and sense in every possible ways. In high level programming languages is absolutely the same, there are… Continue Reading →<\/a><\/p>\n","protected":false},"author":259,"featured_media":21788,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,3],"tags":[582,206,619,62,680,46],"_links":{"self":[{"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/posts\/21789"}],"collection":[{"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/users\/259"}],"replies":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/comments?post=21789"}],"version-history":[{"count":1,"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/posts\/21789\/revisions"}],"predecessor-version":[{"id":21790,"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/posts\/21789\/revisions\/21790"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/media\/21788"}],"wp:attachment":[{"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/media?parent=21789"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/categories?post=21789"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kenscourses.com\/tc101fall2015\/wp-json\/wp\/v2\/tags?post=21789"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}