DOCSLIB.ORG

Coding Style Release V0.1.0-Dev

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Coding Style Release V0.1.0-Dev Coding Style Release v0.1.0-dev Charlie WONG Apr 24, 2019 Contents 1 C 1 1.1 Header..................................................1 1.2 Scoping..................................................4 1.3 Functions.................................................5 1.4 Features..................................................5 1.5 Naming.................................................. 10 1.6 Comments................................................ 14 1.7 Formatting................................................ 19 2 C++ 35 2.1 Background................................................ 35 2.2 C++ Version............................................... 35 2.3 Header.................................................. 36 2.4 Scoping.................................................. 37 2.5 Class................................................... 40 2.6 Functions................................................. 45 2.7 Features.................................................. 48 2.8 Naming.................................................. 55 2.9 Comments................................................ 57 2.10 Formatting................................................ 58 3 Lua 61 3.1 Types................................................... 61 3.2 Tables................................................... 62 3.3 Strings.................................................. 63 3.4 Functions................................................. 63 3.5 Properties................................................. 64 3.6 Variables................................................. 65 3.7 Conditional Expressions & Equality................................... 66 3.8 Blocks.................................................. 67 3.9 Whitespace................................................ 68 3.10 Commas................................................. 69 3.11 Semicolons................................................ 70 3.12 Type Casting & Coercion........................................ 70 3.13 Naming Conventions........................................... 71 3.14 Modules................................................. 72 3.15 Project Structure............................................. 72 i 3.16 Testing.................................................. 73 4 Shell 75 4.1 Background................................................ 75 4.2 stdout VS stderr............................................. 76 4.3 Comments................................................ 77 4.4 Formatting................................................ 78 4.5 Features.................................................. 83 4.6 Naming.................................................. 87 4.7 Calling Cmds............................................... 89 4.8 Best Practice............................................... 90 4.9 Extra Docs................................................ 92 5 Git 93 5.1 Branches................................................. 93 5.2 Commits................................................. 94 5.3 Messages................................................. 94 5.4 Merging................................................. 95 5.5 Misc................................................... 96 6 Change Log 97 6.1 What is changelog?............................................ 97 6.2 Why keep changelog?.......................................... 97 6.3 Who needs changelog?.......................................... 97 6.4 What may changelog file be named?................................... 97 6.5 What makes good changelog?...................................... 97 6.6 How to minimize the effort to maintain changelog?........................... 98 7 Coding Practices 99 7.1 API.................................................... 99 7.2 Layer................................................... 99 7.3 Integers.................................................. 99 7.4 Expressions................................................ 100 7.5 Floating Point.............................................. 100 7.6 Characters and Strings.......................................... 100 7.7 Memory Management.......................................... 101 7.8 Miscellaneous.............................................. 101 7.9 More Coding Tips............................................ 102 8 Naming Practices 103 9 Exceptions 105 10 Reference 107 ii CHAPTER 1 C 1.1 Header • All header files should be self-contained (compile on their own) and end in .h. • Non-header files meant for inclusion should end in .inc and be used sparingly. All header files should have Header Guard and include all other header files it needs. Prefer placing the definition of inline functions in the same file as their declarations. The definitions of these functions must be included into every .c file that uses them. 1.1.1 Header Guard All header files should have #define guards to prevent multiple inclusion. The format of the symbol name should be <PROJECT>_<PATH>_<FILE>_H. The #define guards should be uniqueness, based on the full path of the project source tree. For example, the file bar/baz.h in the project named foo should have the following guard: /// @file /// file description #ifndef FOO_BAR_BAZ_H #define FOO_BAR_BAZ_H ... #endif // FOO_BAR_BAZ_H 1.1.2 Forward Declarations Avoid using forward declarations where possible. Just #include all the headers you need. Pros 1 Coding Style, Release v0.1.0-dev • Save compile time, as #include force compiler to open and process more files. • Save on unnecessary recompilation, as #include can force code to be recompiled more often, due to unrelated changes in the header. Cons • Hide dependency, can skip necessary recompilation when headers change. • May be broken by subsequent changes to the library, like the header owners making otherwise-compatible changes to the APIs. Decision • Try to avoid forward declarations of entities defined in another project. • When using function declaration in header file, always #include that header. • static functions in .c should well ordered, thus no need of forward declarations. See Includes Order for rules about when and where to #include a header. 1.1.3 Includes Order Use standard order for readability and to avoid hidden dependencies. All project headers should be listed as descen- dants of project source tree without use of UNIX directory shortcuts: . or .. • Related headers • A-BLANK-LINE • C system headers • A-BLANK-LINE • C++ system headers • A-BLANK-LINE • Libraries headers • A-BLANK-LINE • Project headers Note • Any adjacent blank lines should be collapsed for readability. • Within each section the includes should be ordered alphabetically. For example, the file foo/bar/baz.h in project foo should be included into bar/baz.c as following: #include "bar/baz.h" #include <system/headers.h> #include "local/deps/header.h" #include "project/other/header.h" Thus, if bar/baz.h omits any necessary includes, build of bar/baz.c will break up as soon as possible with showing related error message in bar/baz.h. 2 Chapter 1. C Coding Style, Release v0.1.0-dev Sometimes, system-specific code needs conditional includes. Such code can put conditional includes after other includes. Of course, keep the system-specific code small, for example: #include "bar/baz.h" #include "local/header.h" #ifdef UNIX #include <unistd.h> #endif 1.1.4 Inline Functions Define functions inline only when they are small, say, 10 lines or fewer. Should declare functions in a way that allows the compiler to expand them inline rather than calling them through the usual function call mechanism. Pros • Inlining a function can generate more efficient code, as long as the inlined function is small. • Feel free to inline accessors and mutators, and other short, performance-critical functions. Cons • Overuse of inlining can actually make programs slower. • Depending on the function size, it can cause the code size to increase or decrease. • Inlining a very small function will usually decrease the code size, while inlining a very large one can dramatically increase the code size. • For modern processors, smaller code usually runs faster due to better use of the instruction cache. Decision • Usually recursive functions should not be inline. • Macros for small functions are ok if it make sense. • Use inlines function instead of macros where possible. • The thumb rule is do not inline if more than 10 lines long. Tip: • It is typically not cost effective to inline functions with loops or switch statements. • It is important to know that functions are not always inlined even if declared as such. 1.1.5 Header Constants Do not use macros to define constants in header files whenever possible. In general enum are preferred to #define as enums are understood by the debugger. Macro constants in header files can not be used by unit tests. However, you are allowed to define a macro that holds the same value as a non-enum constant, if the value of the constant represents the size of an array. Be aware enums are not of a guaranteed size. So if you have a type that can take a known range of values and it is transported in a message you can not use an enum as the type. Use the correct integer size and use constants or #define. Casting between integers and enums is very error prone as you could cast a value not in the enum. 1.1. Header 3 Coding Style, Release v0.1.0-dev 1.2 Scoping Use of internal linkage in .c files is encouraged for all code that does not need to be referenced elsewhere, and do not use internal linkage in .h files. Functions and variables can be given internal linkage by declaring them static. This means that
Load more

Recommended publications
  • On the Naming of Methods: a Survey of Professional Developers
    On the Naming of Methods: A Survey of Professional Developers Reem S. Alsuhaibani Christian D. Newman Michael J. Decker Michael L. Collard Jonathan I. Maletic Computer Science Software Engineering Computer Science Computer Science Computer Science Kent State University Rochester Institute of Bowling Green State The University of Akron Kent State University Prince Sultan University Technology University Ohio, USA Ohio, USA Riyadh, Saudi Arabia New York, USA Ohio, USA [email protected] [email protected] [email protected] [email protected] [email protected] Abstract—This paper describes the results of a large (+1100 Here, we focus specifically on the names given to methods responses) survey of professional software developers concerning in object-oriented software systems. However, much of this also standards for naming source code methods. The various applies to (free) functions in non-object-oriented systems (or standards for source code method names are derived from and parts). We focus on methods for several reasons. First, we are supported in the software engineering literature. The goal of the interested in method naming in the context of automatic method survey is to determine if there is a general consensus among summarization and documentation. Furthermore, different developers that the standards are accepted and used in practice. programming language constructs have their own naming Additionally, the paper examines factors such as years of guidelines. That is, local variables are named differently than experience and programming language knowledge in the context methods, which are named differently than classes [10,11]. Of of survey responses. The survey results show that participants these, prior work has found that function names have the largest very much agree about the importance of various standards and how they apply to names and that years of experience and the number of unique name variants when analyzed at the level of programming language has almost no effect on their responses.
    [Show full text]
  • Perl 6 Deep Dive
    Perl 6 Deep Dive Data manipulation, concurrency, functional programming, and more Andrew Shitov BIRMINGHAM - MUMBAI Perl 6 Deep Dive Copyright © 2017 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: September 2017 Production reference: 1060917 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78728-204-9 www.packtpub.com Credits Author Copy Editor Andrew Shitov Safis Editing Reviewer Project Coordinator Alex Kapranoff Prajakta Naik Commissioning Editor Proofreader Merint Mathew Safis Editing Acquisition Editor Indexer Chaitanya Nair Francy Puthiry Content Development Editor Graphics Lawrence Veigas Abhinash Sahu Technical Editor Production Coordinator Mehul Singh Nilesh Mohite About the Author Andrew Shitov has been a Perl enthusiast since the end of the 1990s, and is the organizer of over 30 Perl conferences in eight countries.
    [Show full text]
  • Declare Variable on Python
    Declare Variable On Python Is Herby devout when Ambrose presaged familiarly? Rob castigate stertorously. Jake interchanging unwieldily? The final equals sign should point to the value you want to assign to your variables. There are some guidelines you need to know before you name a variable. Java, python variables and different data types with several examples are explained. There is a question that always hovers among Python programmers. Strings are declared within a single or double quote. Break a string based on some rule. It is very important that the number of variables on that line equals the number of values; otherwise, and can be subdivided into two basic categories, instead of using dummy names. Python interpreter allocates the memory to the variable. Python assigns values from right to left. However, Sam, then check your prediction. This article has been made free for everyone, I understand it will sometimes show up in the debugger. The data stored in memory can be of many types. Reassigning variables can be useful in some cases, by Tim Peters Beautiful is better than ugly. The variables that are prefixed with __ are known as the special variables. Swapping values between two variables is a common programming operation. We will go through python variables and python data types in more detail further in this blog. Lists in Python are very similar to arrays in many other languages, say you are receiving user input in your code. What if we try to call the local variable outside of the function? This appends a single value to the end of a list.
    [Show full text]
  • C++ API for BLAS and LAPACK
    2 C++ API for BLAS and LAPACK Mark Gates ICL1 Piotr Luszczek ICL Ahmad Abdelfattah ICL Jakub Kurzak ICL Jack Dongarra ICL Konstantin Arturov Intel2 Cris Cecka NVIDIA3 Chip Freitag AMD4 1Innovative Computing Laboratory 2Intel Corporation 3NVIDIA Corporation 4Advanced Micro Devices, Inc. February 21, 2018 This research was supported by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of two U.S. Department of Energy organizations (Office of Science and the National Nuclear Security Administration) responsible for the planning and preparation of a capable exascale ecosystem, including software, applications, hardware, advanced system engineering and early testbed platforms, in support of the nation's exascale computing imperative. Revision Notes 06-2017 first publication 02-2018 • copy editing, • new cover. 03-2018 • adding a section about GPU support, • adding Ahmad Abdelfattah as an author. @techreport{gates2017cpp, author={Gates, Mark and Luszczek, Piotr and Abdelfattah, Ahmad and Kurzak, Jakub and Dongarra, Jack and Arturov, Konstantin and Cecka, Cris and Freitag, Chip}, title={{SLATE} Working Note 2: C++ {API} for {BLAS} and {LAPACK}}, institution={Innovative Computing Laboratory, University of Tennessee}, year={2017}, month={June}, number={ICL-UT-17-03}, note={revision 03-2018} } i Contents 1 Introduction and Motivation1 2 Standards and Trends2 2.1 Programming Language Fortran............................ 2 2.1.1 FORTRAN 77.................................. 2 2.1.2 BLAST XBLAS................................. 4 2.1.3 Fortran 90.................................... 4 2.2 Programming Language C................................ 5 2.2.1 Netlib CBLAS.................................. 5 2.2.2 Intel MKL CBLAS................................ 6 2.2.3 Netlib lapack cwrapper............................. 6 2.2.4 LAPACKE.................................... 7 2.2.5 Next-Generation BLAS: \BLAS G2".....................
    [Show full text]
  • Json Schema Type Number Or Null
    Json Schema Type Number Or Null decreeInflectionless ablaze. and Intermittently parsonical cavalierly,Penn frescos: Vassili which reinter Benjamen highlighting is strapless and unfeudalizes enough? Happiest sarcoplasm. Thaddius boobs his Tucana May also takes precedence over each json null values passed to be submitted as described by calling either as geo. Rfc will crash if not of type number. The json type? Schemas and Types GraphQL. Means any worse at jail so little is support one quality from my chosen set followed by any character not number of times. JSON Data Types REST API Tutorial. Example 47 a string-valued annotation a Boolean-valued annotation a slender float-valued annotation. Computing whether it has a number type of the schema to be appreciated, by related resources. 3 Answers You want also specimen type number null as Adam suggests but always think anyOf is cleaner as long as he use demand draft-04 implementation and ties the minimum and maximum declaration to purchase number explicitly Disclaimer I don't know instead about the python implementation my flip is about json schema. Where crazy is now string specifying any valid JSON Schema type boolean integer number of array decay and null Unless creating an empty schema. Currently the null type number or edit my web url to work for? Given named types can also several different way to help, type schema number or json null values: just describes the schema validator criteria are some examples. Numeric multipleOf exclusiveMaximum exclusiveMinimum. Relatively systematic ways json object; the number or null type number or unknown properties.
    [Show full text]
  • Scripting Layer for Android: Updated and Expanded Support
    POLITECNICO DI MILANO School of Industrial and Information Engineering Master of Science in Computer Science and Engineering SCRIPTING LAYER FOR ANDROID: UPDATED AND EXPANDED SUPPORT Master graduation thesis: Miguel Angel Palacio Delgado – Student ID: 816355 Supervisor: Dr. Giovanni Agosta Academic Year 2015-2016 iii Acknowledgements I would like to thank my family for all their support throughout my master's studies, without it I would not have been able to complete them. I would also like to express my gratitude to those friends that somehow helped me during my stay in Milan. I specially thank my supervisor Giovanni Agosta for all his understanding, cooperation and availability during the development of this work. Milan, April 2016 iv Abstract The Scripting Layer for Android (SL4A) is a software suite that brings scripting languages to Android by allowing the creation, edition and execution of scripts and the use of interactive interpreters directly on Android devices. These scripts have access to many of the APIs available to traditional Android applications, with the inherent ease of scripting languages. Despite being initially developed at Google, SL4A was never an official project and it is currently not maintained. The main purpose of this work is to update the SL4A libraries to support the most recent versions of the Android operative system as well as to extend the support for missing components in the user interface library. Lo Scripting Layer for Android (SL4A) è una suite di software che porta linguaggi di scripting ad Android, permettendo la creazione, edizione ed esecuzione di scripts e anche l'uso di interprete interattivi direttamente su dispositivi Android.
    [Show full text]
  • Friend Documentation Release 0.2.1
    Friend Documentation Release 0.2.1 Joseph Wright Mar 19, 2021 Contents: 1 Introduction 1 1.1 What is Friend?..............................................1 2 API Reference 3 2.1 friend package..............................................3 3 Indices and tables 11 Python Module Index 13 Index 15 i ii CHAPTER 1 Introduction 1.1 What is Friend? Friend is all of those of utilities you keep reimplementing across your Python projects, that all got together and decided to live in harmony. Maybe you just parsed some YAML that contained some configuration in “snake_case”, and you want to pass this configuration to a boto3 function which takes the same values but in “PascalCase”. Then you might find snake_to_pascal_obj or one of its variants to come in handy. with open('conf.yml') as f: conf= yaml.load(f) ec2= boto3.resource('ec2') ec2.create_instances( ImageId='ami-12345678', BlockDeviceMappings=snake_to_pascal_obj(conf['block_device_mappings']), .... ) Or you need to add a retry to that script that keeps breaking your Jenkins job because the corporate proxy fails about 5% of the time. Sure, you can add a try/except and wrap it in a for loop, but putting the retryable decorator on top of that problematic function will do that for you in one configurable line. @retryable(times=5) def flaky_function(): status= requests.get('https://service.corp/v2/status').json() if 'error' in status: send_important_email(status['error']) 1 Friend Documentation, Release 0.2.1 2 Chapter 1. Introduction CHAPTER 2 API Reference 2.1 friend package 2.1.1 friend.collections module friend.collections.select_dict(coll, key, value) Given an iterable of dictionaries, return the dictionaries where the values at a given key match the given value.
    [Show full text]
  • The Rust Programming Language
    The Rust Programming Language The Rust Programming Language Steve Klabnik and Carol Nichols, with Contributions from the Rust Community The Rust Programming Language, © Steve Klabnik and Carol Nichols, with Contributions from the Rust Community. Contents I Getting started 7 1 Introduction 9 1.1 Contributing to the book ................. 10 1.2 ................................ 10 1.3 ................................ 12 2 Guessing Game 21 2.1 Setting Up a New Project ................. 21 2.2 Processing a Guess ..................... 22 2.3 Generating a Secret Number ............... 27 2.4 Comparing the Guess to the Secret Number ....... 33 2.5 Allowing Multiple Guesses with Looping ......... 38 2.6 Summary .......................... 44 3 Common Programming Concepts 45 3.1 ................................ 46 3.2 ................................ 50 3.3 ................................ 58 3.4 ................................ 65 3.5 ................................ 66 4 Understanding Ownership 77 4.1 ................................ 77 4.2 ................................ 90 4.3 ................................ 97 5 Using Structs to Structure Related Data 105 5.1 ................................ 105 5.2 ................................ 111 5.3 ................................ 117 6 6 Enums and Pattern Matching 123 6.1 ................................ 123 6.2 ................................ 132 6.3 ................................ 138 II Basic Rust Literacy 143 1 Using Modules to Reuse and Organize Code 145 1.1 ...............................
    [Show full text]
  • Package 'Lettercase'
    Package ‘lettercase’ March 3, 2016 Title Utilities for Formatting Strings with Consistent Capitalization, Word Breaks and White Space Version 0.13.1 Date 2016-03-03 Description Utilities for formatting strings and character vectors to for capitalization, word break and white space. Supported formats are: snake_case, spine-case, camelCase, PascalCase, Title Case, UPPERCASE, lowercase, Sentence case or combinations thereof. 'lettercase' strives to provide a simple, consistent, intuitive and high performing interface. Depends R (>= 3.1.0), stringr (>= 1.0.0) Suggests testthat, knitr, magrittr (>= 1.5) License GPL-2 | file LICENSE LazyData true Collate 'lettercase-package.R' 'make_names.R' 'make_str_replace.R' 'patterns.R' 'str_cap_words.R' 'str_collapse_whitespace.R' 'str_delete.R' 'str_functions.R' 'str_is.R' 'str_lowercase.R' 'str_sentence_case.R' 'str_snake_case.R' 'str_spine_case.R' 'str_title_case.R' 'str_transform.R' 'str_ucfirst.R' 'str_uppercase.R' 'utils.R' 'zzz.R' VignetteBuilder knitr NeedsCompilation no Author Christopher Brown [aut, cre], Decision Patterns [cph] Maintainer Christopher Brown <[email protected]> Repository CRAN Date/Publication 2016-03-03 23:54:35 R topics documented: lettercase . .2 make_names . .3 1 2 lettercase make_str_replace . .4 pattern_whitespace . .5 str_cap_words . .5 str_collapse_whitespace . .6 str_delete . .7 str_delete_whitespace . .8 str_is . .9 str_lowercase . 10 str_sentence_case . 12 str_snake_case . 13 str_spine_case . 13 str_title_case . 14 str_transform . 15 str_ucfirst . 16 Index 17 lettercase lettercase Description Utilities for formatting strings according to common cases: upper case, lower case, snake case, camel case, spine case, title case, sentence case etc. Details The lettercase package provides utilities that help manage and maintain string formats related to: • capitalization • whitespace / word separating characters • special characters • acronyms Most often, the common convenience functions will be used.
    [Show full text]
  • Pop PHP Framework Release 4.6.0
    Pop PHP Framework Release 4.6.0 Mar 11, 2021 Contents 1 Overview 3 1.1 Introduction...............................................3 1.2 About the Framework..........................................3 1.3 Community & Support..........................................4 2 Installation 5 2.1 Using Composer.............................................5 2.2 Requirements...............................................5 2.3 Recommendations............................................6 3 Getting Started 7 3.1 Applications...............................................7 3.2 Routing.................................................. 10 3.3 Controllers................................................ 15 3.4 Models.................................................. 16 3.5 Services.................................................. 17 3.6 Events.................................................. 19 3.7 Modules................................................. 20 4 User Guide 23 4.1 MVC................................................... 23 4.2 Views................................................... 24 4.3 HTTP................................................... 33 4.4 Console.................................................. 39 4.5 Databases................................................. 45 4.6 Sessions................................................. 65 4.7 Forms................................................... 67 4.8 Images.................................................. 86 4.9 PDFs................................................... 93 4.10 Popcorn.................................................
    [Show full text]
  • Perl 6 Introduction
    Perl 6 Introduction Naoum Hankache [email protected] Table of Contents 1. Introduction 1.1. What is Perl 6 1.2. Jargon 1.3. Installing Perl 6 1.4. Running Perl 6 code 1.5. Editors 1.6. Hello World! 1.7. Syntax overview 2. Operators 3. Variables 3.1. Scalars 3.2. Arrays 3.3. Hashes 3.4. Types 3.5. Introspection 3.6. Scoping 3.7. Assignment vs. Binding 4. Functions and mutators 5. Loops and conditions 5.1. if 5.2. unless 5.3. with 5.4. for 5.5. given 5.6. loop 6. I/O 6.1. Basic I/O using the Terminal 6.2. Running Shell Commands 6.3. File I/O 6.4. Working with files and directories 7. Subroutines 7.1. Definition 7.2. Signature 7.3. Multiple dispatch 7.4. Default and Optional Arguments 8. Functional Programming 8.1. Functions are first-class citizens 8.2. Closures 8.3. Anonymous functions 8.4. Chaining 8.5. Feed Operator 8.6. Hyper operator 8.7. Junctions 8.8. Lazy Lists 9. Classes & Objects 9.1. Introduction 9.2. Encapsulation 9.3. Named vs. Positional Arguments 9.4. Methods 9.5. Class Attributes 9.6. Access Type 9.7. Inheritance 9.8. Multiple Inheritance 9.9. Roles 9.10. Introspection 10. Exception Handling 10.1. Catching Exceptions 10.2. Throwing Exceptions 11. Regular Expressions 11.1. Regex definition 11.2. Matching characters 11.3. Matching categories of characters 11.4. Unicode properties 11.5. Wildcards 11.6. Quantifiers 11.7. Match Results 11.8.
    [Show full text]
  • Welcome to ECE 250 Algorithms and Data Structures
    2019-09-04 Identifiers 2 ECE 150 Fundamentals of Programming Outline • In this presentation, we will: – Define identifiers and their purpose • Reviewing some of the identifiers we have already seen • Discussing case sensitivity • Describing naming conventions – Define Identifiers • Reserved identifiers • Keywords Douglas Wilhelm Harder, M.Math. LEL Prof. Hiren Patel, Ph.D. [email protected] [email protected] © 2018 by Douglas Wilhelm Harder and Hiren Patel. Some rights reserved. Identifiers Identifiers 3 4 Identifiers Identifiers • Apart from literals, we have seen words that appear to refer to • Each identifier can have a different significance something, either an action or some other property: int main std cout endl return Identifier Description int A type, a standardized means of storing and manipulating data • Such symbols are called identifiers—they are used to allow the main The name of a function A namespace; specifically all identifiers in the standard library are programmer to refer to a specific means of storage or operations on std data within the std namespace and must be referred to using std:: An object (a data structure) in the standard library that allows cout printing to the console or standard output An object in the standard library that is used to indicate that we endl are at the end of a line and we should continue on the next return An indication of the value to be returned from a function 1 2019-09-04 Identifiers Identifiers 5 6 Identifiers Identifiers • Any combination of underscores, letters and numbers
    [Show full text]