You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
61 lines
5.3 KiB
XML
61 lines
5.3 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
|
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
|
<channel>
|
|
<title>Introduction on C++ Annotations Version 12.4.0</title>
|
|
<link>https://doc.cyub.vip/cpp/</link>
|
|
<description>Recent content in Introduction on C++ Annotations Version 12.4.0</description>
|
|
<generator>Hugo</generator>
|
|
<language>en</language>
|
|
<atom:link href="https://doc.cyub.vip/cpp/index.xml" rel="self" type="application/rss+xml" />
|
|
<item>
|
|
<title></title>
|
|
<link>https://doc.cyub.vip/cpp/docs/A-First-Impression/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
<guid>https://doc.cyub.vip/cpp/docs/A-First-Impression/</guid>
|
|
<description>Chapter 3: A First Impression Of C++ # In this chapter C++ is further explored. The possibility to declare functions in structs is illustrated in various examples; the concept of a class is introduced; casting is covered in detail; many new types are introduced and several important notational extensions to C are discussed.
3.1: Notable differences with C # Before we continue with the real object-approach to programming, we first introduce some notable differences with the C programming language: not mere differences between C and C++, but important syntactic constructs and keywords not found or differently used in C.</description>
|
|
</item>
|
|
<item>
|
|
<title></title>
|
|
<link>https://doc.cyub.vip/cpp/docs/Friends/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
<guid>https://doc.cyub.vip/cpp/docs/Friends/</guid>
|
|
<description>Chapter 15: Friends # In all examples discussed up to now, we&rsquo;ve seen that private members are only accessible by the members of their class. This is good, as it enforces encapsulation and data hiding. By encapsulating functionality within a class we prevent that a class exposes multiple responsibilities; by hiding data we promote a class&rsquo;s data integrity and we prevent that other parts of the software become implementation dependent on the data that belong to a class.</description>
|
|
</item>
|
|
<item>
|
|
<title></title>
|
|
<link>https://doc.cyub.vip/cpp/docs/IOStreams/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
<guid>https://doc.cyub.vip/cpp/docs/IOStreams/</guid>
|
|
<description>Chapter 6: The IO-stream Library # Extending the standard stream (FILE) approach, well known from the C programming language, C++ offers an input/output (I/O) library based on class concepts.
All C++ I/O facilities are defined in the namespace std. The std:: prefix is omitted below, except for situations where this would result in ambiguities.
Earlier (in chapter 3) we&rsquo;ve seen several examples of the use of the C++ I/O library, in particular showing insertion operator (&lt;&lt;) and the extraction operator (&gt;&gt;).</description>
|
|
</item>
|
|
<item>
|
|
<title></title>
|
|
<link>https://doc.cyub.vip/cpp/docs/Name-Spaces/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
<guid>https://doc.cyub.vip/cpp/docs/Name-Spaces/</guid>
|
|
<description>Chapter 4: Namespaces # 4.1: Namespaces # Imagine a math teacher who wants to develop an interactive math program. For this program functions like cos, sin, tan etc. are to be used accepting arguments in degrees rather than arguments in radians. Unfortunately, the function name cos is already in use, and that function accepts radians as its arguments, rather than degrees.
Problems like these are usually solved by defining another name, e.</description>
|
|
</item>
|
|
<item>
|
|
<title></title>
|
|
<link>https://doc.cyub.vip/cpp/docs/Static-Data-And-Functions/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
<guid>https://doc.cyub.vip/cpp/docs/Static-Data-And-Functions/</guid>
|
|
<description>Chapter 8: Static Data And Functions # In the previous chapters we provided examples of classes where each object had its own set of data members data. Each of the class&rsquo;s member functions could access any member of any object of its class.
In some situations it may be desirable to define common data fields, that may be accessed by all objects of the class. For example, the name of the startup directory, used by a program that recursively scans the directory tree of a disk.</description>
|
|
</item>
|
|
<item>
|
|
<title></title>
|
|
<link>https://doc.cyub.vip/cpp/docs/Strings/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
<guid>https://doc.cyub.vip/cpp/docs/Strings/</guid>
|
|
<description></description>
|
|
</item>
|
|
<item>
|
|
<title>Overview Of The Chapters</title>
|
|
<link>https://doc.cyub.vip/cpp/docs/Overview/</link>
|
|
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
|
<guid>https://doc.cyub.vip/cpp/docs/Overview/</guid>
|
|
<description>Chapter 1: Overview Of The Chapters # The chapters of the C++ Annotations cover the following topics:
Chapter 1: This overview of the chapters. Chapter 2: A general introduction to C++. Chapter 3: A first impression: differences between C and C++. Chapter 4: Name Spaces: how to avoid name collisions. Chapter 5: The string data type. Chapter 6: The C++ I/O library Chapter 7: The class concept: structs having functions.</description>
|
|
</item>
|
|
</channel>
|
|
</rss>
|