Google Code Style Guide—StyleGuide

Google Code Style Guide—StyleGuide

2022-08-30 0 1,633
Resource Number 36594 Last Updated 2025-02-24
¥ 0HKD Upgrade VIP
Download Now Matters needing attention
Can't download? Please contact customer service to submit a link error!
Value-added Service: Installation Guide Environment Configuration Secondary Development Template Modification Source Code Installation

A rigorous code style can give a good impression and better legibility, and in actual development, it is often encountered that it is your own code, and after a period of time you don’t know it at all. Therefore, for beginners, it is necessary to establish good programming habits, which includes code style, such as indenting the first line, adding spaces after keywords, camel nomenclature, etc., the Google open source project styleguide provides code styles including C++, C#, Java, Python and other 10 programming languages, and you can easily write high-quality code by referring to imitation.

 

Google Code Style Guide—StyleGuide插图

Example:

C++ style guide

Header file

All header files should be protected by #define to prevent multiple inclusions, and for uniqueness, they should be based on the full path in the project’s source tree

#ifndef FOO_BAR_BAZ_H_#define FOO_BAR_BAZ_H_…#endif // FOO_BAR_BAZ_H_

Naming conventions

Use a name that describes the object’s purpose or intent

class MyClass {public:int CountFooErrors(const std::vector<Foo>& foos) {int n = 0; Given a finite scope and context for (const auto& foo : foos) {…++n; } }return n; }void DoSomethingImportant() {std::string fqdn = …; The well-known abbreviation for fully qualified domain name }private:const int kMaxAllowedConnections = …; Be clear in context};

Function declarations and definitions

The return type is on the same line as the function name, and the parameters should be on the same line as much as possible

ReturnType ClassName::FunctionName(Type par_name1, Type par_name2) {DoSomething(); …}

Too many parameters can wrap lines

ReturnType LongClassName::ReallyReallyLongFunctionName( Type par_name1, // 4 spaces indented Type par_name2, Type par_name3) { DoSomething(); } 2 spaces indented…

}

 

Google Code Style Guide—StyleGuide插图1

  • Java style guide

    Package name

    Package names are all lowercase, and consecutive words are simply concatenated together (no underscores)

    Correct: com.example.deepspace Error: com.example.deepSpace or com.example.deep_space

    Class name

    Class names are nomenclated with large humps, usually nouns or noun phrases

    Character or ImmutableList

    The naming of test classes begins with the name of the class they are testing

    HashTest or HashIntegrationTest

    Method name

    Method names are nomenclature with small humps, usually verbs or verb phrases

    sendMessage or stop

 

Google Code Style Guide—StyleGuide插图2

  • JavaScript style guide

    Local variable declarations

    Local variables are not usually declared at the beginning of their containment block or block-like construction;

    Each local variable declares only one variable, and does not use let a = 1, b = 2; Such Statements

    Attribute annotations

    The property type must be documented, and the description of the private property can be omitted if the code provides sufficient documentation

    /** My class. */class MyClass {/** @param {string=} someString */constructor(someString = ‘default string’) {/** @private @const {string} */this.someString_ = someString; }}

 

Google Code Style Guide—StyleGuide插图3

Other:

Google Code Style Guide—StyleGuide插图4

资源下载此资源为免费资源立即下载
Telegram:@John_Software

Disclaimer: This article is published by a third party and represents the views of the author only and has nothing to do with this website. This site does not make any guarantee or commitment to the authenticity, completeness and timeliness of this article and all or part of its content, please readers for reference only, and please verify the relevant content. The publication or republication of articles by this website for the purpose of conveying more information does not mean that it endorses its views or confirms its description, nor does it mean that this website is responsible for its authenticity.

Ictcoder Free Source Code Google Code Style Guide—StyleGuide https://ictcoder.com/google-code-style-guide-styleguide/

Share free open-source source code

Q&A
  • 1. Automatic: After making an online payment, click the (Download) link to download the source code; 2. Manual: Contact the seller or the official to check if the template is consistent. Then, place an order and make payment online. The seller ships the goods, and both parties inspect and confirm that there are no issues. ICTcoder will then settle the payment for the seller. Note: Please ensure to place your order and make payment through ICTcoder. If you do not place your order and make payment through ICTcoder, and the seller sends fake source code or encounters any issues, ICTcoder will not assist in resolving them, nor can we guarantee your funds!
View details
  • 1. Default transaction cycle for source code: The seller manually ships the goods within 1-3 days. The amount paid by the user will be held in escrow by ICTcoder until 7 days after the transaction is completed and both parties confirm that there are no issues. ICTcoder will then settle with the seller. In case of any disputes, ICTcoder will have staff to assist in handling until the dispute is resolved or a refund is made! If the buyer places an order and makes payment not through ICTcoder, any issues and disputes have nothing to do with ICTcoder, and ICTcoder will not be responsible for any liabilities!
View details
  • 1. ICTcoder will permanently archive the transaction process between both parties and snapshots of the traded goods to ensure the authenticity, validity, and security of the transaction! 2. ICTcoder cannot guarantee services such as "permanent package updates" and "permanent technical support" after the merchant's commitment. Buyers are advised to identify these services on their own. If necessary, they can contact ICTcoder for assistance; 3. When both website demonstration and image demonstration exist in the source code, and the text descriptions of the website and images are inconsistent, the text description of the image shall prevail as the basis for dispute resolution (excluding special statements or agreements); 4. If there is no statement such as "no legal basis for refund" or similar content, any indication on the product that "once sold, no refunds will be supported" or other similar declarations shall be deemed invalid; 5. Before the buyer places an order and makes payment, the transaction details agreed upon by both parties via WhatsApp or email can also serve as the basis for dispute resolution (in case of any inconsistency between the agreement and the description of the conflict, the agreement shall prevail); 6. Since chat records and email records can serve as the basis for dispute resolution, both parties should only communicate with each other through the contact information left on the system when contacting each other, in order to prevent the other party from denying their own commitments. 7. Although the probability of disputes is low, it is essential to retain important information such as chat records, text messages, and email records, in case a dispute arises, so that ICTcoder can intervene quickly.
View details
  • 1. As a third-party intermediary platform, ICTcoder solely protects transaction security and the rights and interests of both buyers and sellers based on the transaction contract (product description, agreed content before the transaction); 2. For online trading projects not on the ICTcoder platform, any consequences are unrelated to this platform; regardless of the reason why the seller requests an offline transaction, please contact the administrator to report.
View details

Related Source code

ICTcoder Customer Service

24-hour online professional services